We pick REST when we want a simple, cacheable API - which covers most cases just fine.
Related terms
gRPC
High-performance RPC over HTTP/2 with protobuf.
Message Queue
An async broker (e.g.
Microservices vs Monolith
A monolith is simpler, faster to ship, and fine for most teams.
Saga Pattern
Managing a transaction across multiple services without a distributed lock: a sequence of local steps, each with a compensating undo.
The bench this belongs to
Full-stackIf you can describe it, we can build it. React and Next.js on the front, Python or Node behind, Postgres underneath, shipped to somewhere you can afford to run.
