[steeeeeve]

The BFF pattern is just "mostly microservices dedicated to a particular client type".

It makes sense when you have drastically different needs between a desktop client and a mobile client (or maybe for a kiosk client or POS interface)

Hosting a microservice is cheap, it avoids unnecessary workload on backend data stores, and teams can operate with more autonomy if they don't have to cooperatively update APIs in coordination with other groups with differing priorities.

This article really just reads like "I figured out how to do authentication with keycloak using OIDC"

[brtkdotse]

> The BFF pattern is just "mostly microservices dedicated to a particular client type".

If you’re building dedicated APIs for just one client you’ve come full circle and building a monolith with a bunch of extra step. Why not just build a good old web app at that point?

[antihero]

No, you’re not. You’re building specialised tools for each job.

Also with GQL you can separate by business domain as opposed to consumer for example your customer apps/website could use one gateway, and your back office app could use another.

Also, if you have an old monolith in something like rails, and want to build new functionality in something different whilst migrating parts of it over, it makes sense to have a service oriented architecture. A gateway is a layer that exposes all of the services in a unified and consistent manner.

[lmz]

Because some people like the native app experience better?