Posts
58
Comments
103
Trackbacks
10
Every Class Should Be a WCF Service

Actually, no.  Just kidding. ;-)

BUT, that's the view held by a very smart architect from a different school of thought.  We can break down his thoughts a bit further though.  You see, he thinks every class is/should be a component.  So what he's really trying to say is that every component should be a wcf service.  Why?  Because the component services provided by WCF can interop with other languages (if necessary).  This comes via the WS-Death Star.

But don't take my word for it, watch Ron Jacobs interview Juval Lowey.  And close your ears when you hear the comment about TDD.  Don't flip the bozo bit.  He's a really sharp guy.

And remember, if anyone outside Microsoft would be capable of making such a claim about WCF, it would be the RD of Silicon Valley, who was one of the few outside Microsoft to help design WCF.

It may seem like overkill now, but maybe not when processors start shipping with 32 cores on them.

posted on Sunday, October 21, 2007 9:05 PM Print