From the course: Microservices Foundations
Unlock the full course today
Join today to access over 24,900 courses taught by industry experts.
The API layer
From the course: Microservices Foundations
The API layer
- An API layer is often included with microservices architectures, and for a good reason. In a pure microservices architecture, an API layer is nothing more than an aggregated proxy of all of your service offerings. The API layer is used to shield the outside world or even your clients from knowing the structure, organization, or even what exact service is exposing a specific operation, which is actually very useful. The API layer provides a standardized proxy interface that will expose whatever service endpoints and API operations we configure it to expose. We need to be careful here that we aren't transforming the APIs. There's a better way to do that for, say, a mobile client versus a desktop client. The API layer, in my opinion, is a pure proxy. Consider our use cases around scaling up our system under load, or scaling down under a lull. If our service consumption model is one in which we are bound directly to the hosts, managing this infrastructure can become painful, especially…
Contents
-
-
-
-
(Locked)
The services4m 57s
-
(Locked)
The communication dance5m 7s
-
(Locked)
Distribution and scale5m 9s
-
(Locked)
The dangers of latency and gridlock4m 47s
-
(Locked)
Bounded context5m 4s
-
(Locked)
Data domains as a service boundary4m 28s
-
(Locked)
No ACID, only BASE5m 52s
-
(Locked)
The API layer4m 5s
-
(Locked)
-
-
-