SOA and WCF (Windows Communication Foundation) basics


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SOA and WCF (Windows Communication Foundation) basics

  1. 1. Distributed Applications,Web Services, and WCF Yaniv Pessach
  2. 2. About the Presenter As a key member of Microsoft Web Services design team, he was responsible for several of the key patents implemented in the .NET WCF implementation, and is a named contributor to two of the WS-* standards (WS-Discovery and WS-Soap-over-UDP)
  3. 3. Introduction • Web Services − What are they − Why/When to use − How to design for (SOA) − Technologies (legacy) − WCF
  4. 4. Take-away• Web Services enable a new way of building distributed applications in a loosely coupled, independent way• Web Services are based on layers of standards and building blocks which are supported by modern tools• Service Oriented Architecture starts by thinking of the interfaces first; useful enterprise patterns exist• .NET 3.0 introduced Windows Communication Foundation which obsoletes previous communication frameworks• WCF exposes easy access to most WS layers• WCF is based on a Contract, Binding, and Address
  5. 5. Agenda• Web Services Concepts − Introducing the web services concepts − Case study - car dealership – discussion• Building Web Services − Existing building blocks and standards − Principles of SOA − The car dealership architecture – discussion• Web Services Technology − Legacy Technologies − .NET 3.0 / WCF [20] concepts • MiniSample [10] The WCF car dealer
  6. 6. Web Services Properties• Contract defines interaction• Loosely Coupled, avoid dependencies• True Platform Independence• Build, maintain, version, deploy separately• External, Internal, Intra-application
  7. 7. Message Exchange Patterns• Synchronous, Asynchronous, Fire & forget• Uncorrelated/Correlated by transport/Msg• Request/Response (RPC style) vs. Publish / Subscribe vs. One-Way• Multicast• Queuing helps logical fire & forget
  8. 8. The Fjord Dealership• Dealer buys cars, sells cars• Deals with other dealers (get cars on lot)• Verify VIN• Approve Loan• Accept Credit-cards• Etc.
  9. 9. Discussion: Identify WS• In groups, discuss the needed web services − External − Internal − Reliability, performance, data requirements?
  10. 10. Web Services Layers• Base standards• Logical Protocol• Semantic Protocols ws- Orch transact estra tion Ws-policy WSDL ws-security ws-discovery XML SOAP SOAP ws-addr OVER *
  11. 11. Standards• Transports • WS-Reliability• WSDL • WS-transaction• WS-Addressing • WS-Orchestration• Profiles and WS-I • UDDI and WS-• WS-Security Discovery
  12. 12. WS-Addressing• How do we identify a service? EPR• URI or URI + RefProp• <wsa:EndpointReference …> <wsa:Address></wsa:Address> <wsa:ReferenceProperties> <blah:CustomerKey>123456789</fblah:CustomerKey> </wsa:ReferenceProperties> </wsa:EndpointReference>• MessageID, RelatesTo, Action
  13. 13. [WS-]SOAP Over TCP• Wire format• HTTP no longer transport of choice• Performance• No transport level security (https)• Also – Soap Over UDP• Connection sharing [non-standard]
  14. 14. WS-Security• HTTPS only provides transport level security – consider the intermediary• Integrity & confidentiality• Using SOAP header• Username, X.509, Kerberos, XML Sig• Performance vs. TLS ?
  15. 15. WS-Discovery vs. UDDI• Using discovery − .NET vs. java ‘locator’ thinking• UDDI successes and failures − Trust, Service Definition• WS-Discovery − limited scope − Present and Future
  16. 16. SOA• Contract• Encapsulate• Distinct Service• Services exchange data, not share behavior
  17. 17. Loose Coupling• Sacrifices interface optimization• Achieve flexible interoperability• .. And ease of change• .. And does not come naturally
  18. 18. Loose and Tight Coupling Tightly Loosely Msg Style RPC Doc Msg Path Hardcode Route Technology Homogenous Heterogeneous Binding Early, fixed Late Interaction Synchronous Asynchronous Model Reuse Broad applicability Adaptation Recoding Transformation Behavior Anticipated Unexpected* Adapted from ‘loosely coupled’ by Doug Kaye
  19. 19. SOA Patterns• Self Service Client• Service Locator (mostly Javathink)• Broker, Router Variation, XML firewall• Serial and Parallel process pattern• Cached object pattern• Queue and MessageBus• Pub/Sub and distributed observer pattern
  20. 20. SOA Patterns - Implementation• The Message is the Media• Contract First/Contract Second• Fowlerisms − Service Layer − Transform View − Remote Façade − Data Transfer Object − Service Stub [testing]
  21. 21. Architect Fjord WS• Major Services• Building Blocks• Discussion!
  22. 22. Legacy Technologies• Microsoft − RPC − DCOM − .NET 1.1 Remoting − .NET 1.1 WS• Issues − Interoperability − Specific limitations
  23. 23. WCF Presented• Released in .NET 3.0• Diverse Stack• Address / Binding / Contract• Unique Features − Existing building blocks − Ease of implementation, deployment, maint − XML compression, performance
  24. 24. ABC• Address, Binding, Contract − EPR − System bindings, parameters, custom, and custom channels − Interface/class
  25. 25. Topics• Hosting• Channels and extensibility − Existing channels, transports, reliability, security• Profiles• Configuration
  26. 26. Code: Contract[ServiceContract()] public interface ISellCar{ [OperationContract] double price(int vin); [OperationContract (IsOneWay=true)] Void notifyInterest(int vin);}
  27. 27. Code: Client• Svcutil.exe http://...?wsdlusing (CarProxy proxy = new CarProxy()){ double result = proxy.price(617894332);}
  28. 28. Code: Server• Impl: public class CarService: ISellCar {….}• Hosted: something.svc<@Service language=c# class=“….CarService“ %>• SelfHost: using (ServiceHost host = new ServiceHost(typeof(CarService), new Uri("http://..."))) { host.Open(); Thread.Sleep(1000000); host.Close(); }
  29. 29. Config: Server [1]<configuration …. > <system.serviceModel> <services> <service behaviorConfiguration=“CarServiceBehavior" type=…. > <endpoint address="" binding="wsHttpBinding" bindingConfiguration="Binding1" contract=“….ISellCar" /> </service> </services>
  30. 30. Config: Server [2]<configurationName=“CarServiceBehavior" returnUnknownExceptionsAsFaults="True"> </behavior> </behaviors><bindings> <wsHttpBinding> <binding configurationName="Binding1" /> </wsHttpBinding> </bindings> </system.serviceModel></configuration>
  31. 31. Fjord With WCF• Construct pseudo/code• Discussion!
  32. 32. Take-away and SummaryUse Web Services for applications, componentsUse Standards (WS-*) and building blocksArchitect using SOA patterns (routers, locators…)Use .NET 3.0/WCF as communication layerDefine the Contract; configure Binding, and AddressAdd on transports, reliability, security
  33. 33. More Information• more.txt• Contact me –
  34. 34. Backup slides
  35. 35. Web Services Defined• Interoperable machine-to-machine interaction• Using SOAP and XML (some use REST)• Service and Contract• Message• SOA (service oriented architecture)
  36. 36. Sending Out An S.O.A• The Need for SOA• Real world problems• Integration Nightmares• Increasing Complexity
  37. 37. SOAP Sample<soap:Envelopemlns:soap=""> <soap:Body> <getProductDetailsxmlns=…> <productID>827635</productID> </getProductDetails> </soap:Body></soap:Envelope>
  38. 38. WS Layered Usage• External − E.g. process credit card transaction• Internal (‘inside the firewall’) − EAI e.g. accounting to helpdesk apps• Intra-application − Modular design, flexibility, common blocks
  39. 39. Benefits Revisited• Built separately − different teams, timelines, platforms − enable focused teams − minimize accidental dependencies• Deployed separately − Performance, troubleshooting, versioning
  40. 40. Web Services Properties• Contract defines interaction• Loosely Coupled
  41. 41. Standards – Time is right* Source: Computer Networks Fourth Edition , Andrew Tanenbaum
  42. 42. Standards – discuss specifics• Important• Tool support• Too many to choose from
  43. 43. WS-Transaction• Long lived transaction• Problems of 2-phase commit• Based on roll-back• Flexible
  44. 44. WS-Orchestration• Upper level integration• Relies on lower levels• Stabilizing• Think of it as BizTalk
  45. 45. More WFC building blocks• Transactions• Behaviors − Lifetime
  46. 46. Code: Channel Programmingencoder = new TextMessageEncodingBindingElement();transport = new TcpTransportBindingElement();binding = new CustomBinding(encoder, transport);IChannelFactory<IRequestChannel> factory = binding.BuildChannelFactory<IRequestChannel>(); factory.Open();address = new EndpointAddress("net.tcp://");IRequestChannel channel = factory.CreateChannel(address); channel.Open();request = Message.CreateMessage(factory.MessageVersion, "hello");reply = channel.Request(request);Console.Out.WriteLine(reply.Headers.Action);reply.Close(); channel.Close(); factory.Close(); } }
  47. 47. Code: ReliabilityBindingElementCollection bindingElements = new BindingElementCollection(); ReliableSessionBindingElement session = new ReliableSessionBindingElement(); session.Ordered = true; bindingElements.Add(session); bindingElements.Add(new CompositeDuplexBindingElement()); bindingElements.Add(new UdpTransportBindingElement()); Binding playerInfoBinding = new CustomBinding(bindingElements);
  48. 48. Code: ReliabilityBindingElementCollection bindingElements = new BindingElementCollection(); ReliableSessionBindingElement session = new ReliableSessionBindingElement(); session.Ordered = true; bindingElements.Add(session); bindingElements.Add(new CompositeDuplexBindingElement()); bindingElements.Add(new UdpTransportBindingElement()); Binding playerInfoBinding = new CustomBinding(bindingElements);Uri playerInfoAddress = new Uri( "soap.udp://localhost:16000/");using(ServiceHost service = new ServiceHost(typeof(playerInfoService))) { service.AddServiceEndpoint(typeof(IUpdatePlayerInfoContract), playerInfoBinding, playerInfoAddress); service.Open();... // more service code here }
  49. 49. Code: Callback (and duplex)interface IMyContractCallback { [OperationContract] void OnCallback(); }[ServiceContract(CallbackContract = typeof(IMyContractCallback))]interface IMyContract { [OperationContract] void DoSomething(); }public sealed class InstanceContext : CommunicationObject, ... { public InstanceContext(object implementation); ... // More members }class MyCallback : IMyContractCallback { public void OnCallback() {...} } IMyContractCallback callback = new MyCallback(); InstanceContext context = new InstanceContext(callback);IMyContractCallback callback = new MyCallback(); InstanceContext context = new InstanceContext(callback); MyContractClient proxy = new MyContractClient(context); proxy.DoSomething();