Api Gateway - What's the use of an api gateway?
Download as PPTX, PDF5 likes1,748 views
The document discusses the role of an API gateway in the context of stateless applications and microservices. It highlights the benefits of statelessness such as easier testing, scalability, and debugging, while also advocating for using an API gateway to manage features like authentication and call tracing. Furthermore, it presents existing API gateway solutions and introduces the strangler pattern for transitioning from monolithic to microservice architectures.
Api Gateway - What's the use of an api gateway?
- 1. 2017 API Centric What’s the use of an API Gateway?
- 2. 2017 Who Am I ? David Level - Inovia
- 3. 2017 ❖ Stateless application ❖ Microservices / Multiple apis ❖ API Gateway ❖ Strangler Pattern ❖ Existing solutions
- 4. 2017 “In information technology and computer science, a system is called stateful if the way in which it may interact internally or with its environment depends on the condition it is in at a given instant in time.” - Wikipedia
- 5. 2017 Why would you want a stateless app ?
- 10. 2017 Client A Client C Client B Payment service Booking service Search service Archive service REST API REST API REST API REST API
- 13. 2017 Great I’m done with microservices. See you next time!
- 14. 2017 STOP!
- 15. 2017 Does it helps me to handle...
- 16. 2017 Chattiness?
- 19. 2017 Quota?
- 20. 2017
- 21. 2017 Hopefully the API Gateway pattern exists!
- 22. 2017 Client A Payment service Booking service Search service Archive service REST API REST API REST API REST API API Gateway
- 23. 2017 What is this purple thing?
- 25. 2017 This pattern helps with...
- 26. 2017 Managing a single entry point
- 27. 2017 Track calls through correlation IDs
- 28. 2017 Manage quota for all apis
- 29. 2017 Stop failing calls through circuit breaker
- 30. 2017 Should I develop my own one?
- 31. 2017 You can but let’s see existing solutions
- 36. 2017 Hum sounds cool… ...but what about my monolith?
- 40. 2017 Capture and intercept call to the old system
- 41. 2017 https://inovia.fr - @inoviateam David Level - @dlevel57
Editor's Notes
- #2: WHO AM I
- #3: PLAN
- #4: DEFINITION DE STATE
- #5: Why api stateless
- #6: Testabilité
- #7: Scalable
- #8: Debug plus simple
- #9: Split du monolith?
- #10: Diagramme de plusieurs API REST
- #11: Isolation par domaine
- #12: Plus facile à déployer
- #13: Cool on peut se casser?
- #14: Stop on reste assis
- #15: Etes vous capable de...
- #16: Gerer le chattiness
- #17: Gerer l’authentification partagé
- #18: Traquer les call
- #19: Gérer les quotas
- #20: Code spaghetti vers chef d’orchestre
- #21: API GATEWAY Pattern
- #22: LET see how it works
- #23: Mais c’est quoi ce truc violet au milieu
- #24: ZOOM sur l’API Gateway
- #25: Ce pattern sert à ...
- #26: Avoir un seul point d’entrer
- #27: Gerer les correlation ids
- #28: QUOTA
- #29: Circuit breaker
- #30: Développer sa propre api gateway?
- #31: On peut mais
- #32: Presentation des solutions du marché
- #33: FROM nginx LUA MODULE GOOD COMMUNITY EASY TO INSTALL THROUGH DOCKER
- #34: GO Language MIDDLEWARE IN JAVASCRIPT MANAGE ORCHESTRATION MULTIPLE AUTHENTICATION BY ENDPOINT
- #35: CAN HANDLE A LOT OF TRAFIC REALLY RESILIENT => CHAOS MONKEY DEVELOPPED IN JAVA
- #36: ONE SOLUTION FOR ALL YOUR MICROSERVICES SO WHAT SHOULD I DO WITH MY MONOLITH
- #37: STRANGLER PATTERN
- #38: SCHEMA MONOLITH + API GATEWAY
- #39: TRANSITION TO MICROSERVICES
- #40: CAPTURE AND INTERCEPT CALL TO THE OLD SYSTEM
- #41: QUESTIONS?