Why a gateway
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
list what a gateway does for a set of services.
Planned topics
- A gateway is the single public entry point in front of services.
- Routing:
/api/orders/**goes toorders,/api/products/**tocatalog. - Cross-cutting edge concerns in one place: TLS termination, authentication, rate limiting, CORS, request logging, correlation ids.
- Hides internal topology: clients do not know service names or ports.
- Cost: an extra hop, an extra thing to scale and keep highly available.
Draft outline details
Demonstration
diagram: browser → gateway → catalog, orders, inventory, payments on a private network.
Check your understanding
Name two concerns a gateway centralizes.
Show answer
For example TLS termination and rate limiting.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.