Why We Migrated from REST to gRPC (and What Broke)
Service-to-service JSON over HTTP was costing us in latency and schema drift. gRPC fixed two problems and created one.
Tag
4 posts tagged "architecture".
Service-to-service JSON over HTTP was costing us in latency and schema drift. gRPC fixed two problems and created one.
Shared tables, schema-per-tenant, or database-per-tenant? We picked one on purpose. Here is the reasoning.
Every new technology spends innovation tokens. We spend ours deliberately, and keep the rest of the stack delightfully boring.
At-least-once delivery means your jobs will run twice. Design for it instead of hoping it won't happen.