Mar 26 · 10 min read · Series: Backend Engineering Fundamentals · Post 07 of 07 Level: Intermediate · Read time: ~9 min It's 2am. An alert fires. Your service is down. You open your dashboard: CPU is fine, memory is fine.
Join discussion
Mar 26 · 5 min read · I. Introduction: The Observability Problem in Multi-Service AI Apps The rise of multi-service architectures — especially with AI agents spanning multiple runtimes Why logs and metrics alone don't cut
Join discussion
Mar 11 · 5 min read · Understanding the Distributed Tracing Decision Modern .NET applications rarely run in isolation. Between microservices, message queues, caching layers, and external API integrations, a single user req
Join discussionFeb 16 · 12 min read · Trace Context Propagation in Polyglot Microservices When a single user request traverses fifteen different services written in five different languages, understanding what went wrong becomes nearly impossible without proper trace context propagation....
Join discussion
Feb 13 · 6 min read · Observability Best Practices with OpenTelemetry Observability has evolved from a buzzword into a critical requirement for modern distributed systems. As we move through 2025-2026, the complexity of cloud-native architectures demands sophisticated app...
Join discussionFeb 12 · 9 min read · Distributed Tracing: Track Requests Across Microservices In modern distributed architectures, a single user request can traverse dozens of microservices, each adding latency, potential failures, and complexity. When something goes wrong—or worse, whe...
Join discussionJan 26 · 6 min read · BY: Marcus Briggs > Commentator Gold Industry The gold supply chain is undergoing a technological shift. Blockchain is introducing new ways to track metal from refinery to end buyer with a level of verification that paper-based systems were never des...
Join discussion
Jan 19 · 9 min read · APIs rarely fail loudly.Most of the time, they break quietly while dashboards stay green. These silent failures are often the hardest to detect and the most damaging for users. I learned this while dealing with real production traffic. Everything loo...
Join discussion
Jan 17 · 5 min read · Debugging in a monolithic system is usually straightforward. All the code runs inside a single application, so one request maps to one process. When something goes wrong, you typically get a stack trace that clearly tells you which function failed an...
Join discussionDec 22, 2025 · 2 min read · I. Cohen and S. Zhang and M. Goldszmidt and J. Symons and T. Kelly and A. Fox,Capturing, indexing, clustering, and retrieving system history, Proc. of SOSP, 2005. SummaryThis paper presents a method for generating signatures from system states to hel...
Join discussion
