Go Gin Request ID Propagation Across Microservices
Request IDs correlate logs across services without proving caller identity. Start with a clearly defined correctness invariant and workload. Identify the state...
Search
903 results for "Gin"
Go Gin Project Structure for Large APIs With Handlers Services and Repositories
A maintainable Gin API separates transport, business logic, and data access into handlers, services, and repositories, with dependencies pointing inward from...
Go database sql Connection Pool Tuning for Gin APIs
Go's database/sql package manages a connection pool for you, and its default settings are rarely right for a production API. Set a maximum number of open...
Go Gin Structured Logging Middleware With Request IDs
Structured logging middleware for Gin records one machine-readable log line per request, with a request ID that ties together every log message produced while...
Go Gin OpenTelemetry Trace Context Propagation
Distributed trace context links spans from separate services into one request path. Begin with an invariant that the service must preserve even when users...
Docker Compose Profiles for Managing Multiple Environments
Docker Compose profiles let you tag services so they start only when you activate a matching profile. This keeps one Compose file usable for development,...
Docker Log Drivers vs Application Structured Logging
Container log drivers control delivery while structured events preserve application meaning. Start by defining the operational contract: the workload, which...
Nginx Proxy Timeouts and Retry Behavior for Upstream APIs
Nginx has separate timeouts for connecting to an upstream, sending a request, and reading a response, and each one applies to a different stage. Its retry...
Nginx Gzip vs Brotli Compression for JSON APIs
For JSON APIs, gzip is the safe, universally supported default, while Brotli often compresses slightly better at comparable levels but needs an extra Nginx...