Kong

What

Kong is an API gateway.

Text

Routing: Sending requests to different destinations depending on the context or message content.
Transformation: Components responsible for transforming or masking data.
Inbound and outbound traffic monitoring and logging.
Safety policies that add authentication, authorization, and encryption to APIs.

Monolithic Architecture → Microservice Architecture

Pros of Monolith Architecture -

Cons of Monolith Architecture -

Pros of Microservice Architecture -

Cons of Microservice Architecture -

Kong is suite of software that utilizes OpenResty to dynamically configure NGINX and process HTTP requests.

Text

NGINX provides protocol implementations and worker process management,
OpenResty provides Lua integration and hooks into NGINX’s request processing phases, and
Kong itself utilizes those hooks to route and transform requests.

Service entities are abstractions of each of your own upstream APIs and microservices.
Route entities define rules to match client requests. Every request matching a given Route will be proxied to its associated Service.
Each Route is associated with a Service, and a single Service can have many Routes.
Plugins allow you to easily add new features to your API or make your API easier to manage.
Consumers are associated to individuals or applications using your API. They can be used for tracking, access management, and more.