from webservices to apis
TRANSCRIPT
Service-‐Oriented Architecture
From Webservices to API’s and beyond
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Some perspecFve
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 -‐ h@p://www.haufe-‐lexware.com
SOA Manifesto
• Business value over technical strategy • Strategic goals over project-‐specific benefits • Intrinsic interoperability over custom integraFon • Shared services over specific-‐purpose implementaFons
• Flexibility over opFmizaFon • Evolu:onary refinement over pursuit of iniFal perfecFon
From h@p://www.soa-‐manifesto.org
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
SOA Goals
• How to better integrate distributed systems - It quickly became synonymous with a set of protocols and standards: XML, SOAP/HTTP, WS-*
- It also became associated with a set of standardized components: ESB, Registry, Gateway
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Reality Check
Who is the greatest API success story of all time?
Who is the greatest SOA success story of all time?
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
So what went wrong
Integra:on versus Interoperability
IT versus Developer
Control versus Incen:ve
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
SOA versus API
Category SOA API
Business Context • IT driven
• Cost savings • Defined by process
• Business driven • Revenue and BizDev • Defined as product
Perspective • Enterprise Architects • Service Taxonomy
• Canonical Data
• Developers • Developers • Developers!
Non-Functional • Server-to-server • Implicit controls
• Mobile • Consumer-facing
• Web scale
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
The API value chain
• Informaton • Product • Service
Business Asset
• API • SLA • EULA
API Provider • Building App
Developer
• Using API
ApplicaFon • Using App
End-‐User
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
API Management
API
Portal API Owners, Developers, Admin
External and Partner Developers
End User
Service Endpoints
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Connector vs Component
“[REST] is achieved by placing constraints on connector semanFcs where other styles have
focused on component semanFcs.” (Roy Fielding)
Focus is on how things connect, not how they work Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Ensuring Connectors Work Together
1. IdenFficaFon of Resources • URL, URN
2. Resource RepresentaFon • Media types
3. Self-‐describing Messages • HTTP operaFons
4. Hypermedia • Links and forms
Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Remember, why APIs are working
Simplicity Self-‐Service
Low barrier to use Access to valuable resources
h@p://apievangelist.com/2014/05/06/remembering-‐why-‐this-‐whole-‐api-‐thing-‐is-‐working-‐-‐apidays-‐berlin/ Haufe.Group -‐ h@p://www.haufe-‐lexware.com
Where do we go next
Rise of JavaScript in the Enterprise
Hype bubble forms around Microservices
Web APIs the default for IoT
Haufe.Group -‐ h@p://www.haufe-‐lexware.com