[mosselman]

Those first two diagrams about the barista with customers explain it all.

From a customer perspective it is super luxurious to have your own barista. They know my tastes, I never have to wait... But then comes the bill, "€2500 for a cup of coffee?!?". Expecting that you can keep selling €3 cups of coffee in this way is delusional.

Obviously choosing this architecture means you can create 'smooth' conversations from the Front-end's perspective, but it requires an insanely complex system of things underneath it. Expecting that you can efficiently build software like this is also delusional.

Of course there could be valid reasons to do this. As the diagrams indicate, it is about the experience you are providing for people developing applications. I mean a butler level of experience: If you can somehow charge an insane premium for this BFF setup, then have at it. I'd rather grab my own coffee.

Claiming that you are "Simplifying Complex Systems with Backend for Frontends (BFF)" is insane.

[mrkeen]

Try playing with the metaphor a bit more broadly. Is it luxurious for a behaviour to have its own dedicated class, or a c file to have its own header file?

> If you can somehow charge an insane premium for this BFF setup, then have at it. I'd rather grab my own coffee.

In this metaphor, you're the coffee shop owner. If the customer grabs his own coffee, that's fine, but he should probably grab it from home. It is not reasonable to expect the customer to enter the coffee shop, pour his own coffee and operate the cash register.