Blog Tech Chris Richardson · June 15, 2015 Building Microservices: Using an API Gateway API gateway, microservices

twitter
linkedin

The first article in this seven-part series about designing, building, and deploying microservices introduced the Microservices Architecture pattern. It discussed the benefits and drawbacks of using microservices and how, despite the complexity of microservices, they are usually the ideal choice for complex applications. This is the second article in the series and will discuss building microservices using an API Gateway.

When you choose to build your application as a set of microservices, you need to decide how your application’s clients will interact with the microservices. With a monolithic application there is just one set of (typically replicated, load-balanced) endpoints. In a microservices architecture, however, each microservice exposes a set of what are typically fine-grained endpoints. In this article, we examine how this impacts client-to-application communication and proposes an approach that uses an API Gateway.

Editor’s note – This seven-part series of articles is now complete:

Blog Tech Chris Richardson · June 15, 2015 Building Microservices: Using an API Gateway API gateway, microservices

twitter
linkedin

The first article in this seven-part series about designing, building, and deploying microservices introduced the Microservices Architecture pattern. It discussed the benefits and drawbacks of using microservices and how, despite the complexity of microservices, they are usually the ideal choice for complex applications. This is the second article in the series and will discuss building microservices using an API Gateway.

When you choose to build your application as a set of microservices, you need to decide how your application’s clients will interact with the microservices. With a monolithic application there is just one set of (typically replicated, load-balanced) endpoints. In a microservices architecture, however, each microservice exposes a set of what are typically fine-grained endpoints. In this article, we examine how this impacts client-to-application communication and proposes an approach that uses an API Gateway.

Editor’s note – This seven-part series of articles is now complete:

1，Introduction to Microservices
2，Building Microservices: Using an API Gateway (this article)
3，Building Microservices: Inter-Process Communication in a Microservices Architecture
4，Service Discovery in a Microservices Architecture
5，Event-Driven Data Management for Microservices
6，Choosing a Microservices Deployment Strategy
7，Refactoring a Monolith into Microservices

Blog Tech Chris Richardson · June 15, 2015 Building Microservices: Using an API Gateway API gateway, microservices

twitter
linkedin

The first article in this seven-part series about designing, building, and deploying microservices introduced the Microservices Architecture pattern. It discussed the benefits and drawbacks of using microservices and how, despite the complexity of microservices, they are usually the ideal choice for complex applications. This is the second article in the series and will discuss building microservices using an API Gateway.

When you choose to build your application as a set of microservices, you need to decide how your application’s clients will interact with the microservices. With a monolithic application there is just one set of (typically replicated, load-balanced) endpoints. In a microservices architecture, however, each microservice exposes a set of what are typically fine-grained endpoints. In this article, we examine how this impacts client-to-application communication and proposes an approach that uses an API Gateway.

Editor’s note – This seven-part series of articles is now complete:

Introduction to Microservices
Building Microservices: Using an API Gateway (this article)
Building Microservices: Inter-Process Communication in a Microservices Architecture
Service Discovery in a Microservices Architecture
Event-Driven Data Management for Microservices
Choosing a Microservices Deployment Strategy
Refactoring a Monolith into Microservices

Introduction

Let’s imagine that you are developing a native mobile client for a shopping application. It’s likely that you need to implement a product details page, which displays information about any given product.

For example, the following diagram shows what you will see when scrolling through the product details in Amazon’s Android mobile application.

https://www.nginx.com/blog/building-microservices-using-an-api-gateway/