‫So just a quick lecture
‫on a Microservice Architecture
‫you can implement with API gateway.
‫So thanks to API gateway.
‫You can have a single interface
‫for all the microservices in your company,
‫and you can use API endpoints
‫with various resources in the backends.
‫So, you can hide the complexity for your clients.
‫So to say, we have an API gateway
‫and we have a /service1 route,
‫which sends it to a elastic load balancer,
‫which is backing an actual ECS cluster of microservices.
‫Or we can have /docs to send an S3 buckets
‫that contain some study content.
‫For example, the documentation of your service,
‫or /service2 to have an ELB connected
‫to an Amazon EC2 Auto Scaling group fleets.
‫Okay? So all these things allow you to define these routes
‫and use the API gateway as a single URL
‫to connect to these services.
‫Then we can use route 53 to register a domain,
‫instead of the DNS for API gateway.
‫Which also allows us to give us some custom addresses
‫based on the client we have to.
‫So, customer1.example.com for one of the clients,
‫or customer2.example.com for a second clients.
‫And we can apply SSL certificates based on these domains.
‫And we can also within the API gateway,
‫apply forwarding and transformation rules,
‫to modify the incoming data
‫before sending into the backends.
‫So I'm showing you this slide,
‫to just show you the kind of architecture
‫that you can implement with API gateway.
‫The idea is that you want to unify your microservices
‫and give an external unified URL.
‫While hiding all the complexity of, routing to a service.
‫Transforming the data and specifying SSL certificates.
‫All of this is done at the API gateway level.
‫So I hope that is helpful.
‫And I will see you in the next lecture