Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Evolution of API-driven Architectures

35 views

Published on

API history
APIs today
WhereAPIs areheadingto?
API-First-Design
Conclusion

Vortragsfolien vom Digital Xchange 2019, weitere Informationen auf digital-xchange.de

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Evolution of API-driven Architectures

  1. 1. © OPITZ CONSULTING 2018 ¢¢¢ überraschend mehr Möglichkeiten! © OPITZ CONSULTING 2018 Sven Bernhardt Evolution of API-driven Architectures
  2. 2. © OPITZ CONSULTING 2018 API-First-Design Seite 2 About me Sven Bernhardt ¢ Senior Solution Architect @OPITZ CONSULTING Deutschland GmbH ¢ Oracle ACE Director @sbernhardt https://svenbernhardt.wordpress.com/
  3. 3. © OPITZ CONSULTING 2018 Seite 3 Agenda 1 2 3 API history APIs today Where APIs are heading to? API-First-Design 4 Conclusion4
  4. 4. © OPITZ CONSULTING 2018 Seite 4 API history 1 API-First-Design
  5. 5. © OPITZ CONSULTING 2018 Horizontal integration API-First-Design Seite 5 A long time ago in a galaxy far, far away… ¢ APIs in the context of horizontal integration scenarios ¢ Classic System2System integration ¢ Heavy-weight, proprietary protocols ¢ Technical interfaces ¢ Batch processing ¢ Asynchronous interaction patterns
  6. 6. © OPITZ CONSULTING 2018 API-First-Design Seite 6 API Management in times of EAI and SOA https://www.oracle.com/technetwork/articles/soa/weir-3rd-gen-api-mgmt-3787102.html https://tinyurl.com/y5gx45xb
  7. 7. © OPITZ CONSULTING 2018 API-First-Design Seite 7 With the rise of mobile applications, API focus changed Horizontal integration Verticalintegration ¢ End User ”integration” ¢ APIs born from business requirements ¢ Not only who is using the API, but also how an API is being used ¢ Foucs less on reusabilty, but more on providing the data in the right format at the right time ¢ Use of lightweight, standard protocols ¢ (Near) Real-time interaction ¢ Synchronous interaction patterns
  8. 8. © OPITZ CONSULTING 2018 API-First-Design Seite 8 Meaning of APIs and API Management today http://www.soa4u.co.uk/2015/08/oracle-api-management-implementation.html
  9. 9. © OPITZ CONSULTING 2018 API-First-Design Seite 9 Key patterns for implementing API-based solutions API Gateway Backend for Frontend https://microservices.io/patterns/apigateway.html
  10. 10. © OPITZ CONSULTING 2018 Seite 10 APIs today 2 API-First-Design
  11. 11. © OPITZ CONSULTING 2018 API-First-Design Seite 11 Components of API-driven architectures ¢ API Gateway (Runtime) ¢ API policy enforcement ¢ Request routing ¢ API Management Portal/Console (Designtime) ¢ API policy definition ¢ Platform management ¢ API / Developer Portal (Designtime) ¢ API Catalog ¢ View API descriptions ¢ Register for API usage
  12. 12. © OPITZ CONSULTING 2018 API-First-Design Seite 12 REST: The new hope (especially for vertical integrations) https://www.oracle.com/technetwork/articles/soa/weir-3rd-gen-api-mgmt-3787102.html
  13. 13. © OPITZ CONSULTING 2018 API-First-Design Seite 13 Use Case: APIs for modernizing legacy/monolithic applications Monolithic Application CRM Financials HR PM UI Logic Internal networkDMZExternal network Service Implementation Proprietary Protocol API {JSON} API
  14. 14. © OPITZ CONSULTING 2018 API-First-Design Seite 15 Technological evolution singificantly influences the way how applications are built today
  15. 15. © OPITZ CONSULTING 2018 API-First-Design Seite 16 Evolution of application infrastructures: From on-premises to hybrid, scalable and elastic infrastructures ¢ Kubernetes is the new de-facto application platform ¢ Container orchestration platform developed by Google ¢ Abstracts Infrastructure, Network & Storage ¢ Cloud technologies enable infinite scalability and elasticity on a infrastructure level
  16. 16. © OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 17 Evolution of application architectures: From Monoliths to Cloud- Native Apps Monolithic architectures µService architectures Serverless architectures f(a1) f(a2) f(a3) f(a4) f(b4)f(b3) f(b2)f(b1) f(c3) f(c4) f(c2)f(c1) f(d1) f(d2) f(d3) f(d4) Ø Single application Ø Mixed data from different business context Ø Mixed business logic Ø Application consists of different µService Ø Business logic and data belong to a bounded business context Ø Application consists of multiple functions Ø Fine-granular logic for a specific step, data resides externally
  17. 17. © OPITZ CONSULTING 2018 Seite 18 Where APIs are heading to? 3 API-First-Design
  18. 18. © OPITZ CONSULTING 2018 API-First-Design Seite 19 Next-gen API Management solutions are needed
  19. 19. © OPITZ CONSULTING 2018 API-First-Design Seite 20 Example 3rd Gen API Platform: Oracle API Platform Cloud Service ¢ Designed API first ¢ Implemented Cloud-Native ¢ Supports full API lifecycle ¢ Problem: Gateway is not a real µGateway
  20. 20. © OPITZ CONSULTING 2018 API-First-Design Seite 21 API Gateway solutions should be capable to cover as many scenarios as possible API- Gateway API- Gateway Client Client Monolith Microgateway Serverless f(a1) f(a2) f(a3) f(a4) f(b4)f(b3) f(b2)f(b1) f(c3) f(c4) f(c2)f(c1) f(d1) f(d2) f(d3) f(d4) Cloud 1 Cloud 2 API- Gateway Client
  21. 21. © OPITZ CONSULTING 2018 API-First-Design Seite 22 Real 3rd Gen API Gateway Platform: Kong API Management ¢ Gateway can be scaled horizontally by adding new nodes ¢ Modular approach powered by plugins that are configured using a RESTful API ¢ Runs on any infrastructure and supports various deployment topologies https://konghq.com/solutions/gateway/
  22. 22. © OPITZ CONSULTING 2018 x API-First-Design Seite 23 Microgateways and Kubernetes: Ingress Controller Ingress An API object that manages external access to the services in a cluster, typically HTTP. Ingress can provide load balancing, SSL termination and name-based virtual hosting. https://kubernetes.io/docs/concepts/services-networking/ingress/ ¢ Ingress traffic = North-South traffic ¢ Protecting your exposed Kubernetes services ?
  23. 23. © OPITZ CONSULTING 2018 API-First-Design Seite 24 Microgateways and Kubernetes: Service Mesh Service Mesh A platform that makes service-to-service communication more reliable, secured and observable. ¢ Service Mesh approach for East-West traffic ¢ Mutual TLS scenarios ¢ Identity Token propagation ¢ … ¢ Protecting internal Service communications
  24. 24. © OPITZ CONSULTING 2018 x API-First-Design Seite 25 GraphQL: The new kid on the block ¢ GraphQL was originally invented by Facebook and released in 2015 ¢ GraphQL supports typed schema definitions, defines a consumer orientied query language and provides a runtime to execute the respective queries ¢ Consumers exactly receive, what they are asking for Describe: type Conference { name: String description: String host: [Company] } Ask: { conference(name: “DIX2019") { description } } Get results: { "conference": { "description": “Awesome conference" } }
  25. 25. © OPITZ CONSULTING 2018 API-First-Design Seite 26 When does GraphQL come into the game? ¢ GraphQL is good to reduce application chattiness, which occurs due to limitations of REST-based APIs https://blog.apollographql.com/graphql-vs-rest-5d425123e34b
  26. 26. © OPITZ CONSULTING 2018 API-First-Design Seite 27 It shouldn‘t be a decision, if using REST or GraphQL, but have them both co-existing ¢ Think of GraphQL as an API Composition layer for your existing REST APIs ¢ API compositions using GraphQL is a concrete Backend For Frontend implementation https://microservices.io/patterns/data/api-composition.html
  27. 27. © OPITZ CONSULTING 2018 Seite 28 Conclusion 4 API-First-Design
  28. 28. © OPITZ CONSULTING 2018 API-First-Design Seite 29 With great power, comes great responsibility ¢ Don‘t be a sinner by implementing API Sandwich architectures! ¢ Choose your API Gateway architecture wisely ¢ Don‘t add API layers that do not add value to the solution ¢ Think about the way how you implement your APIs ¢ There‘s not only black and white https://de.slideshare.net/luisw19/7-deadly-sins-of-api-at-devoxxuk-2019
  29. 29. © OPITZ CONSULTING 2018 Seite 30API-First-Design Q & A
  30. 30. © OPITZ CONSULTING 2018 ¢¢¢ überraschend mehr Möglichkeiten! @OC_WIRE OPITZCONSULTING opitzconsultingWWW.OPITZ-CONSULTING.COM Seite 31 Contact me! Sven Bernhardt Senior Solution Architect | Oracle ACE Director OPITZ CONSULTING Deutschland GmbH Kirchstrasse 6, 51647 Gummersbach, Germany Phone: +49 172 2193529 Mail: sven.bernhardt@opitz-consulting.com @sbernhardt https://svenbernhardt.wordpress.com API-First-Design
  31. 31. © OPITZ CONSULTING 2018 API-First-Design APIs are omnipresent in today‘s digital world!
  32. 32. © OPITZ CONSULTING 2018 API-First-Design Seite 33 APIs are important part of Micorservices architectures µ Customers µ Orders µ Loyalty µ Finance µ Logistics Web Shop Portal Micro-UIs µ Customers µ Orders µ Loyalty µ Finance µ Products µ Products APIs
  33. 33. © OPITZ CONSULTING 2018 API-First-Design Seite 34 Data-driven APIs in Big Data architectures Analytics App 1 Analytics App 2 Analytics App 3 Analytics App 4 Landing Zone Data Pipeline / Data Ingestion Metadata Store Content Store Rawdata Store Big Data Platform DataLake Integration Services APIs

×