Hello everyone. In this article, we are going to see what an and how it is used for communication in a . We will also see the benefits and drawbacks of the API Gateway pattern. Then we will look at a pattern called which is a variant of the API Gateway pattern, and conclude the article by looking at cases when we need either method. API Gateway is Client-Server Microservices architecture Backend for Front End, Let's get started. API Gateway The API Gateway is a server that handles many functionalities in a single place for the clients to interact. It also works as a between your client applications and the back-end microservices architecture reverse proxy There could be multiple clients that call the server APIs, and the API Gateway is the component that routes requests to the relevant microservice and then gets the response and send it to the client. It handles all the cross-cutting features like , etc in a single place instead of us implementing these functionalities in every single microservices. Moreover, it can consolidate and aggregate the data across aggregating multiple microservices using a single endpoint for clients to communicate. Security, Logging, Caching Before the evolution of Microservices architecture, most of the systems used a Monolith pattern and we could even handle the cross-cutting concerns in a single or couple of servers. But with microservices, we cannot afford to handle cross-cutting concerns in each of the microservices which will make things slower with a larger memory footprint degrading the performance of the system. Backend For Frontend We’ve discussed the API Gateway. This approach is fine if we have a single client on the web or mobile. If our application is used by multiple clients like web, mobile, IoT, etc, it is not a good idea to use a single API Gateway for all types of clients. The process will get cumbersome fast and it could bloat up the API Gateway service by making it a single Monolith service. The better approach for this type of scenario is to use a separate API Gateway for each client type this architectural pattern is called the Backend for FrontEnd (BFF) pattern and it has become a buzzword. The BFF pattern is an architectural paradigm, a variant of the API gateway pattern and it comprises multiple back-ends that are designed to meet the demands of specific front-end applications, such as desktop, browser, and native-mobile applications, IoT devices, etc. Also published here.

API Gateway vs Backend for Frontend (BFF): Use Cases, Similarities and Divergencies

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

5 Major Factors Impacting the Evolution of APIs

Tips for Developers to Survive API-First

52 Stories To Learn About Api Gateway

A Guide to API Gateways: Unveiling Advantages, Disadvantages, and Vendor Comparisons

A Look at Use of API Gateways When Creating Complex Systems

A Quick Guide For Creating a Serverless Application with AWS Lambda and API Gateway

5 Major Factors Impacting the Evolution of APIs

Tips for Developers to Survive API-First

52 Stories To Learn About Api Gateway

A Guide to API Gateways: Unveiling Advantages, Disadvantages, and Vendor Comparisons

A Look at Use of API Gateways When Creating Complex Systems

A Quick Guide For Creating a Serverless Application with AWS Lambda and API Gateway

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps