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.

Austin API Summit 2019 - APIs, Microservices, and Serverless: The Shape of Things to Come

410 views

Published on

A look at the growth of APIs, the influence of microservices and serverless, and the new enterprise API platform stack including API profiles, multiple API styles, and data management

Published in: Software
  • Be the first to comment

Austin API Summit 2019 - APIs, Microservices, and Serverless: The Shape of Things to Come

  1. 1. APIs, Microservices, and Serverless – The Shape of Things to Come Austin API Summit 2019 James Higginbotham james@launchany.com @launchany Photo by Christian Fregnan on Unsplash
  2. 2. 2@launchany Introduction • Executive API Consultant • API strategy and execution • Based in Colorado Springs • Across multiple verticals: – Commercial Insurance – Healthcare – Hospitality – Finance and Banking – Travel – Airline
  3. 3. 3@launchany The API Landscape
  4. 4. 4@launchany APIs Solve a Variety of Use Cases Customer Experience Worker Experience Supplier/Partner Experience Integration Utility
  5. 5. 5@launchany APIs Require Different Interaction Styles Request/ Response Request/ Acknowledge Batch-Based Publish/ Subscribe Message Streaming
  6. 6. 6@launchany Today’s Popular API Styles
  7. 7. 7@launchany API Eventing and Streaming Styles
  8. 8. 8@launchany REST for Course-Grained APIs “The REST interface is designed to be efficient for large grain hypermedia data transfer, optimizing for the common case of the Web, but resulting in an interface that is not optimal for other forms of architectural interaction.” - Roy Fielding - https://www.ics.uci.edu/~fielding/pubs/dissertation/software_arch.htm#sec_1_5
  9. 9. 9@launchany Moving the Mindset From “vs.” to “and” + + + + +
  10. 10. 10@launchany The Enterprise API Platform Journey Photo by Neil Iris on Unsplash
  11. 11. 11@launchany APIs Often Start Simple
  12. 12. https://launchany.com/canvas
  13. 13. 13@launchany Serverless: Rapid API Deployment and Event Processing Source: https://github.com/stefanprodan/gh-actions-demo
  14. 14. 14@launchany As the Organization Grows, Complexity Increases
  15. 15. 15@launchany How we think of our data strategy Source: https://upload.wikimedia.org
  16. 16. 16@launchany What our data strategy really looks like http://www.settao.com/agile-database-development/
  17. 17. 17@launchany Today’s Data Pipeline: From ETL to ELQT
  18. 18. 18@launchany Proper Data Management is Critical to an API Platform
  19. 19. 19@launchany The Evolving API Platform Photo by Ashkan Forouzani on Unsplash
  20. 20. 20@launchany Capabilities and Outcomes First, API Design Next • Track a project from start to completion • Subdivide a project into tasks • Mark tasks as completed • View incomplete tasks • View active projects • View archived projects • Add collaborators to a project • POST /projects • POST /projects/{projectId}/tasks • POST /projects/{projectId}/tasks /{taskId}/complete • GET /tasks?status=incomplete • GET /projects?status=active • GET /projects?status=archived • POST /projects/{projectId}/members
  21. 21. 21@launchany Separate API Interfaces (API Profiles) from Implementation (API Styles)
  22. 22. 22@launchany Application-Level Profile Semantics (ALPS) as the Interface https://tools.ietf.org/html/draft-amundsen-richardson-foster-alps-02
  23. 23. 23@launchany The Evolving Enterprise Platform
  24. 24. 24@launchany API Descriptions Captures API Style Specifics (OpenAPI)
  25. 25. 25@launchany API Descriptions Captures API Style Specifics (GraphQL)
  26. 26. 26@launchany API Descriptions Captures API Style Specifics (gRPC)
  27. 27. 27@launchany Describing Events Using AsyncAPI (https://asyncapi.com)
  28. 28. 28@launchany Describing Streaming Data Using AsyncAPI (Apache Avro)
  29. 29. 29@launchany The Evolving Enterprise Platform
  30. 30. 30@launchany APIS.json Captures the API Profile (http://apisjson.org/)
  31. 31. 31@launchany DISCO for Late Binding of Instances (http://www.open-disco.org)
  32. 32. 32@launchany The Evolving Enterprise Platform
  33. 33. 33@launchany The Journey Toward an Enterprise API Platform Offers API Inventory API Orders API Identity API Accounts API Rewards API Partners Internal Developers Public App Developers Customers Third-party Approved Apps Redeem Svc Register Svc Avail Offers Svc Check Inv Svc Ship Receive Svc Create Order Svc Order History Svc Profile Svc Permissions Svc Friends n Fam Svc Redemption Stream New Acct Stream Inv Low Stream Order Proc Stream
  34. 34. 34@launchany FaaS is the Integration Glue • APIs deliver capabilities through commands and queries • Events and streaming provide extensibility • Function-as-a-Service (FaaS) is the integration glue Rewards API Redeem Svc Register Svc Redemption Stream Redemption Event onRedemptionEvent() APIs Capabilities (Services) Streaming & Eventing Functions-as-a-Service & Stream Processors Redemption Processor
  35. 35. 35@launchany The Shape of Things to Come Photo by Garidy Sanders on Unsplash
  36. 36. When APIs Meet Jobs-To-Be-Done { … "_links": { “self": {"href": "/approval-requests/d796f2d0eb72492bb088"}, “approve": {"href": "/approval-requests/d796f2d0eb72492bb088/approve"}, “decline": {"href": "/approval-requests/d796f2d0eb72492bb088/decline"}, }, … } { "event": { "type": "approved", … } }
  37. 37. 37@launchany The History of Low Code/No Code Source: https://www.youtube.com/watch?v=I5WEH8jh8Hk Client-Server SOA/SOAP
  38. 38. 38@launchany The Future is API Integration (again)
  39. 39. 39@launchany Preparing for Tomorrow Photo by x ) on Unsplash
  40. 40. 40@launchany Preparing for Tomorrow’s API Platform - Today 1. Use the right API styles to fit the need (“and” principle) 2. Keep your platform tidy and machine readable: – API descriptions (OpenAPI/Blueprint) – Event descriptions (AsyncAPI) – Capabilities (ALPS) – API profiles (APIS.json) – Runtime availability and guarantees (DISCO) 3. Consider data management and governance part of your API practice 4. Push an adopt-first culture that values “lines of code unwritten” 5. Evaluate tools to accelerate integrating APIs, events, and streams
  41. 41. 41@launchany James Higginbotham james@launchany.com @launchany https://launchany.com/canvas https://apideveloperweekly.com

×