4 ms·
Ideally you wouldn't have (or need) microservices! I'd rather deal with a monolithic rails app any day. However, assuming you've got them, BFF means only one g
by danielheath 4y ago
Ideally you wouldn't have (or need) microservices! I'd rather deal with a monolithic rails app any day.
However, assuming you've got them, BFF means only one group has to get the following right:
* User authentication
* Web performance analytics
* A/B testing
* More difficult bits of HTTP (fast TLS, prefetch, streaming responses)
If you have microservices but no BFF, you're pretty much stuck with your page being substantially rendered via js. Maybe that's okay for some things? I sure don't like it.
- respondo2134 4y ago>> I'd rather deal with a monolithic rails app any day. if your app gets "bigger" this can work OK, but I've found they typically get "wider" and then any work on the monolith gets really painful and slow. My last two gigs have been at opposite ends of the spectrum and it's kind of a "pick your poison" situation.