Engineering_Blog
These posts follow a strict arc: problem, architecture, failure point, resolution, and business impact. They are written for engineering hiring teams that want production-grade thinking, not tutorial-style demos.
Why App Runner was useful for first delivery, where it stopped fitting these workloads, how I moved the AI gateway to ECS Express Mode and the Go load balancer to regular ECS, and which AWS alternatives remained viable.
- Problem under hard constraints
- Architecture data flow
- Breaking point and bottleneck fix
How I shifted from request-coupled execution to queue-worker isolation to keep execution throughput stable under burst traffic.
- Problem under hard constraints
- Architecture data flow
- Breaking point and bottleneck fix
A breakdown of how I hardened a Go load balancer against backend flapping with health-aware routing and controlled retry behavior.
- Problem under hard constraints
- Architecture data flow
- Breaking point and bottleneck fix
How I designed incident lifecycle rules and alert deduplication in NetPulse to keep uptime signals trustworthy.
- Problem under hard constraints
- Architecture data flow
- Breaking point and bottleneck fix
1. Open content/blog/index.ts and add a new object in blogPosts.
2. Follow this structure exactly: hook → architecture → stressTest → bottleneckResolution → businessImpact.
3. Add optional stress-test screenshots to public/ and set stressTest.screenshotUrl.