@techiehustler
Hi, I’m techiehustler — a software engineer and tech entrepreneur passionate about building scalable systems, clean architectures, and high-performance applications.
I work extensively with .NET, cloud platforms, automation, and distributed systems, and I enjoy turning complex problems into simple, reliable solutions. Here, I share practical insights, real-world learnings, and engineering patterns from my day-to-day work — covering backend development, system design, testing, and performance optimisation.
Always learning. Always building.
Nothing here yet.
Apr 14 · 8 min read · Why Endpoint-Only Load Tests Miss Transaction Completion Failures When load testing distributed, event-driven systems, it's common to measure request throughput, response latency, and HTTP error rates at the API boundary. Those metrics are necessary,...
Join discussionApr 14 · 10 min read · Why Endpoint-Only Load Tests Miss Transaction Completion Failures Endpoint response times and request success rates are necessary—but not sufficient—indicators of system health for distributed and event-driven systems. When your architecture relies o...
Join discussionApr 14 · 8 min read · Why Endpoint-Only Load Tests Miss Transaction Completion Failures When teams benchmark systems with load tests they often measure request throughput and request-level latency to judge capacity and stability. Those endpoint-only metrics are valuable, ...
Join discussionApr 14 · 9 min read · TL;DR Measuring only HTTP success (2xx) under load misses a large class of failures where the API request succeeded but the end-to-end transaction did not complete. For distributed, event-driven systems the real correctness signal is transaction comp...
Join discussionApr 14 · 9 min read · Why Endpoint-Only Load Tests Miss Transaction Completion Failures Endpoint-level load tests (hammering HTTP endpoints to measure throughput and latency) are necessary but not sufficient for distributed, event-driven systems. They tell you how well th...
Join discussion