A Node.js service kept getting OOMKilled, but only on Tuesdays. The batch job was a red herring. The real problem was a lazy cache eviction strategy that nobody thought to question.
- Published On
memory
Tags
consulting (69)debugging (28)architecture (27)developer-experience (22)reliability (20)devops (14)ai (11)performance (10)observability (8)code-quality (7)database (6)microservices (5)security (5)technical-debt (5)engineering-culture (4)testing (4)productivity (4)kubernetes (4)postgres (4)ci-cd (3)databases (3)postgresql (3)infrastructure (3)tooling (3)configuration (2)resilience (2)cost-optimization (2)dependencies (2)nodejs (2)code-review (2)deployment (2)opentelemetry (2)monitoring (2)javascript (2)goals (2)data (1)websockets (1)project-management (1)mcp (1)finops (1)multi-tenant (1)authorization (1)terraform (1)dns (1)opinion (1)api-design (1)memory (1)error-handling (1)secrets-management (1)webhooks (1)containers (1)environments (1)queues (1)cloud (1)orm (1)refactoring (1)on-call (1)alerting (1)incident-management (1)typescript (1)distributed-systems (1)caching (1)platform-engineering (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)migration (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)