How do async ap is survive in a rest world
•Download as PPTX, PDF•
0 likes•149 views
The document discusses how asynchronous APIs can survive in a REST-based world. It describes how Async APIs use an event-driven approach compared to the request-reply model of REST. The AsyncAPI specification aims to describe event-driven APIs similarly to how OpenAPI describes REST APIs. The document demonstrates how Async and REST APIs can work together using an example setup with an API gateway, manager, and message broker to connect an HTML page and Node.js client via published topics.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to How do async ap is survive in a rest world
Similar to How do async ap is survive in a rest world (20)
More from Red Hat
More from Red Hat (20)
Recently uploaded
Recently uploaded (20)
How do async ap is survive in a rest world
- 1. How do Async APIs Survive in a REST World? Luca Ferrari EMEA Solution Architect 1
- 2. Past and present 2 Some of the topics I recently presented about: Luca Ferrari 3scale ... now Red Hat ... now IBM
- 3. What is Async API ? The model 3
- 4. Why Async APIs ? 4 from …
- 5. Why Async APIs ? 5 … to
- 6. Why Async APIs ? 6 example: Kafka Kafka Strengths: ● Real Time Data Pipeline ● High-throughput ● Fault-tolerant ● Low Latency ● Scalability Kafka Limits: Kafka is not optimized to provide API consumers with friendly access to real time data. Difficult to expose and re-use API oriented tools for Kafka
- 7. Why Async APIs ? 7 example: Kafka Kafka Strengths: ● Real Time Data Pipeline ● High-throughput ● Fault-tolerant ● Low Latency ● Scalability Kafka Limits: Kafka is not optimized to provide API consumers with friendly access to real time data. Difficult to expose and re-use API oriented tools for Kafka
- 8. What is AsyncAPI ? AsyncAPI and Open API Spec 8 ● AsyncAPI - derived from OpenAPI ● Similarities: ○ Definitions - similar schemas ○ Well-defined set of operations (HTTP methods vs publish/subscribe) ○ Similar security models for web interactions ● Differences ○ Semantic differences between clients (publisher/subscriber vs client/server) ○ Different concepts (e.g. cookies) ○ Different data payloads
- 9. Why AsyncAPI ? Features 9 ❖ Being able to describe: ➢ Event-driven microservices ➢ IoT APIs ➢ Streaming APIs ❖ Some supported protocols: ➢ MQTT ➢ AMQP ➢ WebSocket ➢ Kafka ➢ Stomp ➢ NATS ➢ HTTP ➢ JMS
- 10. Kafka condensed All the moving parts 10
- 11. REST or ASYNC ? 11 Request-reply vs. event-driven Synchronous & ephemeral Low composability Low tolerance to failure Best practices evolved as REST Asynchronous and persistent Decoupled Highly composable High tolerance to failure Best practices are still evolving
- 12. REST and ASYNC ! 12 Common concerns ● API contracts ○ Differentiated levels of service ○ Security: who can consume what topic, what operation ● Ease of consumption ○ Search a catalog of Topics, labels ○ ‘Try it out’s for data formats ● Monitoring, Analytics ● Monetization ○ What to price? ○ Who does what today?
- 13. Demo ! 13
- 22. OpenShift Container Platform Demo setup 22 HTML5 page API Gateway API Manager HTTP Bridge AMQ Streams AsyncAPI NodeJS client
- 23. Closing Takeaway notes 23 ▸ Difference between Sync and Async APIs ▸ Objective of AsyncAPI project ▸ Sync and Async APIs can play together
- 24. Closing Takeaway notes 24 ▸ Difference between Sync and Async APIs ▸ Objective of AsyncAPI project ▸ Sync and Async APIs can play together Go out and be part of the community ! https://github.com/strimzi https://github.com/asyncapi
- 25. linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHat Red Hat is the world’s leading provider of enterprise open source software solutions. Award-winning support, training, and consulting services make Red Hat a trusted adviser to the Fortune 500. Thank you 25
Editor's Notes
- Check meet kafka slides
- Check meet kafka slides
- Check meet kafka slides
- Check meet kafka slides