Michele recently wrote a lengthy but deliciously thorough article on MSDN (hat tip: Lynn) called Application Deployment Strategies which identifies five core scenarios for using Windows Communication Foundation within a distributed application. Those scenarios include:
- Enterprise web services. Think secure, interoperable services that may also utilize new-ish WS* standards such as WS-AtomicTransaction and WS-ReliableMessaging.
- Web 2.0 services. These are your POX or REST services with a look at JSON and RSS/ATOM.
- Intranet applications. These services which live inside your own organization may use something like TCP as a transport. Or, if you’re like my company, even the internal web service standard is SOAP over HTTP.
- Queued messaging. If you have asynchronous or offline messaging needs, you can look at MSMQ with WCF. She also touches on “pub/sub” scenarios and discussing building ESB-like capabilities.
- Workflow services. If you’re building workflow-based applications using WF, there are considerations for exposing services from those workflows.
For each scenario, Michele nicely calls out the implementation characteristics (e.g. hosting environment, authentication, etc), configuration details, and a set of common questions and answers (e.g. “What other credential types are supported for web services?” or “When should I use a reliable session?”).
The formatting of the article itself makes it a bit tricky to understand which header topic you’re currently under, but, I’m sure you’re smart enough to figure it out.
Richard Seroter's Architecture Musings 