2. About me:
❏ Front-end intern
❏ Working on Icatu Seguros Project
❏ https://github.com/octaviocarpes
❏ https://www.linkedin.com/in/octavio-pitrez-carpes-bbbab0148/
3. What is a API Gateway?
An API Gateway its an single entry point that receives requests
to its internal systems.
4. What is its purpose?
An API Gateway can have many roles, it can act like this five
examples:
❏ Filter: it can filters the requests made by different
environments (Mobile, Browser ...)
❏ Single Entry Point Layer: for the many others APIs that
you wish to expose
❏ Essential Component: to APIs management
❏ Traffic Router and Rate Limit
❏ Security Mechanism: logs, authentications and goes on
5. Difference between a API
Gateway and a API Manager
❏ A API Gateway is mainly used for security, while a API
Manager is used for analyze your system.
❏ Any API Manager has a API Gateway imbued within itself.
8. Better Development!
With many services being used and controlled by the gateway
you can see which services are not being used so much and,
with that in mind, you can adapt other services that are more
used.
9. Buffer Zone!
Any attack against a service, controlled by a gateway, won't
affect your whole system. If the service goes down and the user
makes a request to it the gateway won't show to the user that
the service is down.
10. Activity Log!
With every service passing through the gateway it is possible to
prevent future errors.
12. Let's imagine we have an online
store:
❏ We have different types of clients: mobile and browser
❏ The complexity of the services is different eg: one service
just fetch data from a DB while other makes a product
recommendation to the client.