It's better to use a monolithic API Gateway when your team is small and you want to keep things simple. Also, if all your clients need pretty much the same data, then a single gateway makes a lot of sense. You dont want to add extra complexity with BFFs if you don't need to.

So, we're building the API layer for a new product, and everyone's arguing about using one big API Gateway or doing the Backend for Frontend (BFF) thing. A single gateway looks easier to handle at first, which is nice. But I'm worried it'll slow things down and get tangled up as we grow and different apps come out. On the flip side, BFFs give us more wiggle room and can be tweaked for each specific app. The catch is, we'd have more services to look after and maybe some repeated code. What do you all think? When does one approach really beat the other, especially thinking about how big our team is and how much we plan to scale?