Kонструируем микросервисную архитектуру на Symfony и связываем с Kong
0 likes133 views
This document discusses microservices architecture and using Kong as an API gateway. It begins with an introduction to microservices vs monolithic architecture. Then it covers implementing microservices with RabbitMQ and Symfony. Next, it discusses security considerations for microservices. It introduces Kong and how it provides a centralized gateway for microservices. Finally, it covers setting up Kong with Docker and using its management API and plugins.
Kонструируем микросервисную архитектуру на Symfony и связываем с Kong
- 1. Конструируем microservices architecture на Symfony и связываем с Kong Alex Deemann [email protected]
- 2. Конструируем microservices architecture на PHP и связываем с Kong Alex Demcheko [email protected]
- 3. Конструируем microservices architecture на Whatever и связываем с Kong Alex Demcheko [email protected]
- 4. Alex Demchenko Lazy Ants founder & CEO
- 9. RabbitMQ Implementation - API consistency
- 10. RabbitMQ Implementation - API consistency - Resource-intensive tasks
- 12. - Blocking I/O Gateway API: Guzzle
- 13. Blocking I/O Gateway API: Guzzle
- 14. Gateway API: ReactPHP NON - Blocking I/O
- 15. Gateway API: ReactPHP NON - Blocking I/O
- 19. NAMSHI | JOSE https://github.com/namshi/jose This library provides a lightweight implementation of the JWS (JSON Web Signature) specification
- 22. Gateway API
- 25. Gateway API: KONG uses
- 26. ● Common functionality is duplicated across services. Gateway API: before KONG
- 27. Gateway API: before KONG
- 28. ● Common functionality is duplicated across services. ● Systems tend to be monolithic and hard to maintain. Gateway API: before KONG
- 29. ● Common functionality is duplicated across services. ● Systems tend to be monolithic and hard to maintain. ● Difficult to expand without impacting other services. Gateway API: before KONG
- 30. ● Common functionality is duplicated across services. ● Systems tend to be monolithic and hard to maintain. ● Difficult to expand without impacting other services. ● Productivity is inefficient because of system constraints. Gateway API: before KONG
- 31. Gateway API: with KONG
- 32. Gateway API: with KONG ● Kong centralizes and unifies functionality into one place.
- 33. Gateway API: with KONG ● Kong centralizes and unifies functionality into one place. ● Build efficient distributed architectures ready to scale.
- 34. Gateway API: with KONG ● Kong centralizes and unifies functionality into one place. ● Build efficient distributed architectures ready to scale. ● Expand functionality from one place with a simple command.
- 35. Gateway API: with KONG ● Kong centralizes and unifies functionality into one place. ● Build efficient distributed architectures ready to scale. ● Expand functionality from one place with a simple command. ● Team is focused on the product, Kong does the REST.
- 36. KONG: Setup with Docker Run the Cassandra container or PostgreSQL
- 37. Run the Kong container KONG: Setup with Docker
- 38. 1. 8000 - non-SSL enabled proxy layer for API requests. 2. 8443 - SSL enabled proxy for API requests. 3. 8001 - RESTful Admin API for configuration. You will use this port to administrate your Kong installation. 4. 7946 - This is used for Kong clustering. KONG: Used ports
- 40. KONG Management RESTful API
- 41. KONG Management RESTful API
- 42. Send API request
- 43. KONG: PLUGINS