A creative roadmap for backend devs.

Everyone knows how to add a cache. Almost no one has a written-down invalidation strategy before shipping.

An in-depth exploration of backpressure in distributed systems — why it arises, how it impacts stability and throughput, and the strategies engineers use to handle it effectively.

Mike Mwita

Ambitious Software Developer

Passionate about building reliable software systems, scalable backends, and clean developer experiences across web, cloud, and distributed environments.

Download full CV (PDF)

Summary

I am a driven and enthusiastic software developer with a strong interest in backend systems, cloud infrastructure, and developer tooling. I enjoy designing and building software that is maintainable, scalable, and easy to reason about.

I have hands-on experience collaborating in cross-functional teams, contributing to open-source projects, and delivering production-ready systems using modern tools and practices.

Come to think of it , Slack is not a chat app. It’s a multi-tenant distributed system wearing a friendly UI. The lessons from how it handles isolation, fanout, and noisy neighbors apply far beyond messaging.

You type a username. Before you finish, it’s already taken. No network call. No lag. How?

Cache stampede is when your own users become the attack. The fix is not more cache — it is treating the cache miss path like a critical section.