Using APIs without the KONG architecture

The KONG tool provides a centralized solution for the API Management mechanism; if you don't have KONG configuration at the server level for APIs, then you have to implement common functionalities of API Management across your multiple microservices. This means code duplicity will be increased and it will be difficult to maintain and expand without impacting other microservices. The systems tend to be monolithic, as you can see in the following diagram about these common functionalities without the KONG configuration:

Common functionality codes are distributed across the APIs. It is very difficult to ...

Get Mastering Spring Boot 2.0 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.