Each application scenario includes a skeleton view of a deployment topology of particular scenario and a skeletal representation of possible or recommended solution, with analysis of the solution applied.
For me this are visual patterns of scenarios and solution, where you can quickly scan what scenario pattern fits your application (or closest fit) and what is the possible or recommended solution.
But let me be clear here, the recommended solution will not necessarily be 100% fit to your scenario - but treat it as baseline and customize it to your scenario appropriately.
As part of our patterns & practices WCF Security Guidance Project - Yesterday we released a set of Application Scenarios.
Intranet
- Intranet – Web to Remote WCF Using Transport Security (Trusted Subsystem TCP)
- Intranet – Web to Remote WCF Using Transport Security (Trusted Subsystem, HTTP)
- Intranet – Web to Remote WCF Using Transport Security (Original Caller, TCP)
- Intranet – Windows Forms to Remote WCF Using Transport Security (TCP)
- Internet – Web to Remote WCF Using Transport Security (Trusted Subsystem)
- Internet – Windows Forms Client Calling WCF Using Message Security
~Later