Downloaded 19 times
![Connector vs Component
“[REST] is achieved by placing constraints on
connector semantics where other styles have
focused on component semantics.”
(Roy Fielding)
Focus is on how things connect,
not how they work
Haufe.Group - http://www.haufe-lexware.com](https://image.slidesharecdn.com/soa-fromwebservicestoapis-160925204204/75/SOA-From-Webservices-to-APIs-14-2048.jpg)
Uploaded byHolger Reinhardt
SOA - From Webservices to APIs
The document discusses the evolution of service-oriented architecture (SOA) and APIs. It notes that SOA aimed to better integrate distributed systems through standards like XML, SOAP, and WS-*, but it became associated with complex implementations. In contrast, APIs are business-driven, defined as products by developers to generate revenue, and focused on simplicity and self-service. The document argues that APIs have succeeded where SOA failed because of their developer-centric approach compared to SOA's enterprise focus on control and standards compliance.
More Related Content
![Java Web Services [1/5]: Introduction to Web Services](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter1-130106065040-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to SOA - From Webservices to APIs
![Number_Guessing_Game_Dsbsbssbzboc[1].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/numberguessinggamedoc1-251206215042-a076fc05-thumbnail.jpg?width=640&height=640&fit=bounds)
SOA - From Webservices to APIs
- 1. Service-Oriented Architecture From Webservicesto API’s and beyond Haufe.Group - http://www.haufe-lexware.com
- 2.
- 3. Some perspective 1999 –Web Meets the Enterprise 2000-03 – Rise of SOA 2004-07 – SOA Golden Age 2008-11 – A New Paradigm 2012- APIs Prevail Haufe.Group - http://www.haufe-lexware.com
- 4. SOA Manifesto • Businessvalue over technical strategy • Strategic goals over project-specific benefits • Intrinsic interoperability over custom integration • Shared services over specific-purpose implementations • Flexibility over optimization • Evolutionary refinement over pursuit of initial perfection From http://www.soa-manifesto.org Haufe.Group - http://www.haufe-lexware.com
- 5. SOA Goals • Howto better integratedistributed systems - It quickly became synonymous with a set of protocols and standards: XML, SOAP/HTTP, WS-* - It also became associated with aset of standardized components: ESB, Registry, Gateway Haufe.Group - http://www.haufe-lexware.com
- 6. Reality Check Who isthe greatest API successstory of all time? Whois the greatest SOA successstory of all time? Haufe.Group - http://www.haufe-lexware.com
- 7. So what wentwrong Integration versus Interoperability IT versus Developer Control versus Incentive Haufe.Group - http://www.haufe-lexware.com
- 8. SOA versus API CategorySOA API Business Context • ITdriven • Cost savings • Defined byprocess • Business driven • Revenueand BizDev • Defined as product Perspective • EnterpriseArchitects • Service Taxonomy • CanonicalData • Developers • Developers • Developers! Non-Functional • Server-to-server • Implicit controls • Mobile • Consumer-facing • Web scale Haufe.Group - http://www.haufe-lexware.com
- 9.
- 10.
- 11.
- 12. The API valuechain • Informaton • Product • Service Business Asset • API • SLA • EULA API Provider • Building App Developer • Using API Application • Using App End-User Haufe.Group - http://www.haufe-lexware.com
- 13. API Management API Portal API Owners, Developers, Admin Externaland Partner Developers End User Service Endpoints Haufe.Group - http://www.haufe-lexware.com
- 14. Connector vs Component “[REST]is achieved by placing constraints on connector semantics where other styles have focused on component semantics.” (Roy Fielding) Focus is on how things connect, not how they work Haufe.Group - http://www.haufe-lexware.com
- 15. Ensuring Connectors WorkTogether 1. Identification of Resources • URL, URN 2. Resource Representation • Media types 3. Self-describing Messages • HTTP operations 4. Hypermedia • Links and forms Haufe.Group - http://www.haufe-lexware.com
- 16. Remember, why APIsare working Simplicity Self-Service Lowbarrier to use Access to valuable resources http://apievangelist.com/2014/05/06/remembering-why-this-whole-api-thing-is-working--apidays-berlin/ Haufe.Group - http://www.haufe-lexware.com
- 17. Where do wego next Rise of JavaScript in the Enterprise Microservices Web APIs the default for IoT Haufe.Group - http://www.haufe-lexware.com
- 18.
Editor's Notes
- #8 The SOA Approach Micro: examines specific application to application flows, inserts a pattern Focuses on integrating systems, mashing them together Totalitarian: thou shalt follow the rules, punitive The API Approach Macro: views resources are parts of a greater machine, organic Focuses on allowing distinct parts (resources) to interoperate Democratic: incentive-based, empowering