Following my earlier post about WCF service design guidelines, I've created some WCF code snippets to simplify the implementation of services, operations, messages and data contracts.

Microsoft has released an article comparing the performance of WCF and .NET 2.0 distributed application technologies such as ASMX web services, WSE web services, COM+ applications and .NET 2.0 remoting. The results are surprising.

I'm currently writing a service that needs to provide long-lived callback behaviour to a large number of clients. In this case, the WCF session semantics are not appropriate and so I can't use the ServiceContractAttribute's CallbackContract property.

I've recently begun playing around with developing an SOA solution using WCF. My focus is on implementing a service that is loosely coupled, autonomous, highly configurable and reusable. I might tell you more about it in a later blog, but for now I want to describe some of the design issues involved.

If you are interested in service-oriented architecture, including analysis and design, then have a look at this book: Service-Oriented Architecture Concepts, Technology and Design Thomas Erl, Prentice Hall, 2005. Full details here...