This document provides an overview of API gateways and their role in microservice architectures. It begins with a brief history of monolithic architectures and how microservices emerged as a solution. It then defines key concepts like APIs, gateways, and how they relate. The main points are: 1) An API gateway acts as a single entry point and centralizes request routing, protocol translation, and provides cross-cutting features like authentication, monitoring and security for internal microservices. 2) Gateways help reduce complexity and overhead by encapsulating microservices and allowing transformations, while also improving reusability and security. 3) Examples of API gateway tools are provided, as well as a proposed activity, before concluding

1. Api Gateway
A safe journey for finding little treasures!

2. Hello!
Enyert Viñas here!
Welcome!
We are here to present the third session of our
meetup.

3. “
“We build our systems in the same way we build our cities: over time,
without a plan, on top of ruins.”
Ellen Ullman

4. Guideline
◆ A Little of history and concepts!
◆ What is API Gateway? Why?
◆ Two samples
◆ A little game

5. 1.
A little history and concepts
Pre-microservice -> Microservice

6. History
Now20132000

7. Monoliths!
1. Built as a single unit
2. Frequently consists on
three parts: DB, FE, BE
3. High coupling
4. Frequently uses only one
tech stack

8. Evolution!
Microservices appear as a solution for the
exponential complexity of technology requirements

9. API
◆ Application Programming
Interface
◆ Rules + Specifications and
protocols*
◆ Communications between
differents software
components
More Definitions...
Gateway
◆ An opening that can be
closed by a gate (Wikipedia)
◆ A means of access or entry
to a place
(Taken from Google Translate)

10. API Gateway!
Ok we are closer now! 8-)

11. How microservices and API Gateway are related

12. 2.
Whats is API Gateway? & Why
The central point of our thing

13. And an API Gateway is...
Centralized Component
◆ An API Gateway is a
single entry point
◆ The main
responsibilities are
request routing,
composition and
protocol transaction
Encapsulator
◆ Exposes a
functionality, but
protect the internal
logical complexity of
every component to
the clients
Multiple functionalities
◆ Authentication
◆ Traffic control
◆ Serverless trigger
◆ Logging
◆ Transformations
◆ Analytics
◆ Monitoring
◆ More...

14. Why API Gateway?
Encapsulation
Protects the internal
microservice organization
Transformations
It can make transformations
over the requests and
responses required from the
different components
Security
We can protect our internal
components using a security
pluggable component in the API
Gateway component
> Variety != > complexity
Provides the capacity to add
more functionalities without
incrementing the complexity of
internal layers
Reusability
We can reuse the same API
Gateway for multiple
functionalities, so we don’t have to
rebuild the same feature several
times
Reduced overhead
More requests between several
internal microservice components
produce overhead. API Gateway
reduces the number of requests
made in our multi-channel layers

15. 3.
Two samples
Wonderful tools and great opportunities to
learn...

16. Trending solutions!

17. Trending solutions!

18. 4.
A little game
Tied-up!

19. Thanks!
Any questions?
You can find me at
@enyert
enyert.vinas@gmail.com

20. Credits
Special thanks to all the people who made this event
possible:
◆ Everis Peru SAC
◆ Meetup followers and collaborators