3 ms·

I have no FAANG experience but I’ll comment if that’s alright. A few potential talking points: BFF pattern allows you to separate concerns, have different tea

I have no FAANG experience but I’ll comment if that’s alright. A few potential talking points: BFF pattern allows you to separate concerns, have different team topologies and development methodologies, and technical standards and values for different parts of the system. Leadership may appreciate your arguments if you can put them context of enabling teams to advance independently and have different priorities which could otherwise be in conflict. An example could be efficiency gains from fronted / client oriented teams not having to switch language to work on BFF if using node. Another could be testing standards / code coverage for platform APIs may be higher than necessary for more experimental client related work.

faizshah 4y ago
This is great! The main questions I’m anticipating are “why cant we just improve the backend apis” and “why do we want the frontend team to own an Service?” I think your point of focusing on how the requirements of the BFF team differ from the backend team could be a strong argument. Like the backend apis have to be low latency and consistent whereas the frontend apis can accept some higher api latency in exchange for lower page load speeds and eventual consistency via caching.