4 ms·
Microservices with an api proxy were nice for me when I ran a small team because different subteams could use their preferred language, and set their own releas
by sneak 4y ago
Microservices with an api proxy were nice for me when I ran a small team because different subteams could use their preferred language, and set their own release cadence, and autoscale separately. It wasn’t so much about scale or quality as it was letting different teams independently build/deploy/maintain/scale different routes on the same public api server hostname.
We also got to centralize the read cache memory pool in the frontend, so each backend service is not potentially caching duplicate stuff, saving on memory across the org.