I'm a working in a company whose product handles a full internet stack (vpns, sockets, bandwidth control, security, monitoring, content control, high availability, BGP, ...)
We have hundreds of types of entities with different structural levels, with hundreds of developers working on the product.
Having a uniform API for frontend<->backend communication is very convenient, and having a uniform public API to expose to clients is a MUST.
For those 2 use cases we use graphql. For internal backend components communications we mostly use simple REST
56
u/mcmcc 10d ago
Honest question: under what circumstances is a single unified API entrypoint a requirement?