Welcome to SOA with WCF Blogs. SOA with WCF is where you would find answers to common business problems of the real-world.
Why SOA?
First of all, I don’t wish to start dog fight over the definition of SOA. The bottom line is- it can save your bottom line. Often it is not the technology alone that can resolve business problem(s). You do need arts (Practices, Patterns, Governance, Architecture Frameworks, etc.) along with the right set of technologies (i.e. WCF) to solve those problems. SOA would play the part of arts here. Of course, don’t forget the people (leaders) who would bring arts and science together!
SOA built on 3R principles- Reduce (cost and time to market the product/service), Reuse(the services) and Refactor (to simplify and to encourage reusability) can motivate decision makers to move the applications from Silo to Services to Shared Services. Take small but decisive steps at a time for successful SOA implementation.
Why WCF?
With the release of .NET 3.5, Microsoft came a long way in it’s promise to empower Service Oriented Architecture in addition to unifying other distributed technologies (asmx, WSE, Remoting, Messaging, etc.) and solving interoperability problems. The ABC (address, binding, contract) of WCF made it simple and unique to gain acceptance among developers. WCF is designed to decouple the implementation from it’s consumers. Developers and Architects are powered with endless possibilities on how to deliver (bindings) the service with agreed upon contract (interface based).