APIs & Gateways

Each API style exists because a previous one hurt — REST for cacheable resources, GraphQL for clients that need many shapes, gRPC for fast typed internal calls, WebSockets for server push, webhooks for event delivery across organisations — and each carries a failure mode you inherit the moment you choose it.

One edge component that authenticates, rate-limits, routes, logs and reshapes every inbound request so the services behind it do not each reinvent those concerns — valuable exactly as long as it stays an edge and does not absorb the business logic, aggregation and orchestration that turn it back into the monolith.