Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

SOA - From Webservices to APIs

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Próximo SlideShare
Introduction to webservices
Introduction to webservices
Cargando en…3
×

Eche un vistazo a continuación

1 de 18 Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

A los espectadores también les gustó (20)

Anuncio

Similares a SOA - From Webservices to APIs (20)

Más reciente (20)

Anuncio

SOA - From Webservices to APIs

  1. 1. Service-Oriented Architecture From Webservices to API’s and beyond Haufe.Group - http://www.haufe-lexware.com
  2. 2. Haufe.Group - http://www.haufe-lexware.com
  3. 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. 4. SOA Manifesto • Business value 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. 5. SOA Goals • How to 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. 6. Reality Check Who is the greatest API successstory of all time? Whois the greatest SOA successstory of all time? Haufe.Group - http://www.haufe-lexware.com
  7. 7. So what went wrong Integration versus Interoperability IT versus Developer Control versus Incentive Haufe.Group - http://www.haufe-lexware.com
  8. 8. SOA versus API Category SOA 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. 9. Haufe.Group - http://www.haufe-lexware.com
  10. 10. Haufe.Group - http://www.haufe-lexware.com
  11. 11. Haufe.Group - http://www.haufe-lexware.com
  12. 12. The API value chain • 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. 13. API Management API Portal API Owners, Developers, Admin External and Partner Developers End User Service Endpoints Haufe.Group - http://www.haufe-lexware.com
  14. 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. 15. Ensuring Connectors Work Together 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. 16. Remember, why APIs are 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. 17. Where do we go next Rise of JavaScript in the Enterprise Microservices Web APIs the default for IoT Haufe.Group - http://www.haufe-lexware.com
  18. 18. Microservices Haufe.Group - http://www.haufe-lexware.com

Notas del editor

  • 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

×