Enforce error handling, validation, timeouts, and observability for REST backends.
npx skills add https://github.com/gabi-agent/openretro --skill backend-gabi-agent
Please help me install this Agent Skill. Skill: Backend Source: https://github.com/gabi-agent/openretro/tree/main/skills/backend Command: npx skills add https://github.com/gabi-agent/openretro --skill backend-gabi-agent
Backend systems often suffer from unpredictable failures, security gaps, and poor observability. This Skill provides a comprehensive set of practices to ensure reliable, secure, and observable services across modern architectures.
Implement these backend best practices in your API to improve reliability, security, and observable performance.
High-intent search queries and answers about installing and using this skill.
Robust error handling in REST APIs requires logging stack traces internally while returning generic messages to clients. Implement structured error responses containing code, message, and request ID, failing fast on bad input and alerting on unexpected 500 errors.
Input validation in microservice backends should validate everything from outside early, including query params, headers, body, and path params. Whitelist valid input and enforce strict size limits on all inputs to prevent bad data from processing.
Timeouts for database queries and external calls require deterministic limits set across the entire request pipeline and background jobs. Configure retry patterns using exponential backoff with jitter, idempotency keys, and circuit breakers to prevent cascading failures.
Yes, this backend reliability guidance applies to REST and microservice backends across modern architectures. It enforces secure, scalable services by standardizing database connection pooling, cache stampede prevention, rate limiting, and comprehensive observability.
Liveness, readiness, and startup probes ensure fast, cheap health checks during graceful shutdowns. Graceful shutdowns stop accepting new requests, drain existing connections, and handle signals properly to maintain service stability during deployments.
Structured logging alone provides limited backend observability without metrics, tracing, and alerting. Comprehensive observability requires combining structured logs with request IDs, distributed tracing, dashboards, and monitoring to fully secure and scale services.
nicholasgriffintnPlan backend systems, APIs, and data models with structured architecture decisions.
duylinhdang1998Implement structured logging, Prometheus metrics, OpenTelemetry tracing, and Grafana dashboards for distributed services.
cenjieSecure REST APIs with authentication, rate limiting, CORS, and input validation.
spencerpaulyAdd Sentry error tracking and performance monitoring to web applications.
