The BFF pattern[1] may be more useful today to many, due to various types and sizes of devices and different sorts of integrations. MVC can be used in its plac

The BFF pattern[1] may be more useful today to many, due to various types and sizes of devices and different sorts of integrations. MVC can be used in its place, but it would often introduce unnecessary complexity, e.g. additional controllers. MVC works for contextually equivalent interaction, which is still very useful, too. Mostly just do what makes sense. The challenge is, as it has been, how to be flexible, smart, and forward-looking, but developing quickly for what’s needed now. But whether you’re coding a quick prototype or designing a large project (which is risky because a feedback loop from all users may be longer), focusing too much on the how and specifics instead of the overall experience may get you into trouble later. For example, you could have what sounds ideal: microservices, individual teams each working on them focused on their own goals, powering a site with the latest, well-used JS framework, able to deploy quickly and developing quickly with a lot of fun-but-professional-looking communication, and end up with a slow, broken application. [1]- https://samnewman.io/patterns/architectural/bff/ https://samnewman.io/patterns/architectural/bff/