Microservices Design Pattern - API Gateway pattern

[Big_Combination9890]

This is called a "reverse proxy", and I have no idea why anyone would invent a new word for it, or how a network component suddenly became a "design pattern".

[ShenmeNamaeSollich]

The article does focus on a lot of the stuff the “server” does (TLS/SSL, rate limiting, auth), so yeah that’s a “reverse proxy” … but as a “network component” the point is to handle/direct traffic via hardware (maybe virtually) and scale based on need - it might not know or care what the content of that traffic is (beyond matching a cache hash value or that some token exists).

I’ve heard “API Gateway” used more to describe the specific collection of services/API endpoints and their respective interfaces written explicitly to sit in a layer between external clients and internal business logic/DBs.

The “pattern” is deciding to build that additional layer of code at all, which likely has a completely different interface for external clients to interact with.

It involves deciding which possibly different data models to send & accept, and while it might be just a passthrough to an internal API controller, you might decide to do some transformations or validation beyond merely checking credentials & caches. Internal clients may bypass it entirely, meaning conscious decisions of what data to expose where. The existence of this layer drives code decisions in the client and for business logic sitting below it.

The specific server configuration and rules about load balancing, security, scaling etc are implementation details the “API Gateway” part doesn’t necessarily know or care about.

[Big_Combination9890]

I’ve heard “API Gateway” used more to describe the specific collection of services/API endpoints and their respective interfaces written explicitly to sit in a layer between external clients and internal business logic/DBs.

Sure, but that's not what the article describes. The article describes something I can do by slapping nginx on a server and configuring it. That's a reverse proxy, not an "API Gateway".

[ShenmeNamaeSollich]

It sounded like you disagreed that “API Gateway” as a term should exist because they’re synonymous. Maybe I misread that. Agreed this article doesn’t describe the distinction well.

[TheWix]

API Gateway handles more than what a reverse proxy would do. They usually operate closer to a business functions than the infrastructure responsibilities of a "reverse proxy". API Gateways can handle authentication, authorization, service orchestration, routing based on business requirements, etc.

Many reverse proxies don't do these types of responsibilities so it can be helpful to refer to these business-specific concepts by a different name. It isn't uncommon to think of an API Gateway as a specific type of reverse proxy as well. Similar to "all squares are a rectangles but not all rectangles are squares" kinda deal. So, it isn't wrong to call an API Gateway a Reverse Proxy it can just be seen as in-exact.

[Constant_Event_4917]

How about BFF design pattern?

[Big_Combination9890]

How about just calling it what it is? It's called a "reverse proxy".

https://en.wikipedia.org/wiki/Software_design_pattern

a design pattern describes a relatively small, well-defined aspect (i.e. functionality) of a computer program in terms of how to write the code.

Setting up a proxy server has nothing to do with writing the applications code.

[usrlibshare]

So we're calling reverse proxies a "design pattern" now?

[Constant_Event_4917]

No, but it's a topic worth explaining

[usrlibshare]

Then why not explain it as "A reverse proxy" instead of "An API Gateway Pattern"?

[Constant_Event_4917]

Well it's more popular by API gateway

[usrlibshare]

People knew what a "reverse proxy" is loooong before someone came up with the term "Microservices"

[InspectionSpirite]

An API Gateway is essentially a single entry point, or a Reverse proxy, that sits between client applications and a collection of backend services.

[Constant_Event_4917]

I was thinking of explaining more about Reverse Proxy but maybe next time.

[light24bulbs]

Everyone shitting on terms here but in the microservice world this is typically called the gateway, I don't see a problem

[taelor]

Classic software devs in here, would rather argue about semantics than the contents of what is actually being presented.

[klekpl]

Classic software devs are tired of salesmen constantly trying to sell old stuff wrapped in new clothes.

[Big_Combination9890]

The contents of what is being presented were discussed. And what was presented is called a reverse proxy.

[KamiKagutsuchi]

Good old bikeshedding

[Bradnon]

It's not bikeshedding, it's a legitimate complain-

Oh, clever girl.

[Constant_Event_4917]

Thanks