--- title: "ScaleDojo (@scaledojo) | Hashnode" description: "ScaleDojo (@scaledojo) writes on Hashnode. Read their latest articles and follow their work." url: "https://hashnode.com/@scaledojo" --- @scaledojo # ScaleDojo @scaledojo · Joined September 2026 ### [Caching Strategies Explained: Cache-Aside vs Write-Through vs Write-Back](https://scaledojo-engineering.hashnode.dev/caching-strategies-explained-cache-aside-vs-write-through-vs-write-back?utm_source=hashnode&utm_medium=feed) Add a cache is the most common answer in a system design interview. It is also the answer that gets the most follow-up questions. Where does the data go first? What happens when the cache and the data 4 min read · [scaledojo-engineering.hashnode.dev](https://scaledojo-engineering.hashnode.dev/caching-strategies-explained-cache-aside-vs-write-through-vs-write-back?utm_source=hashnode&utm_medium=feed) [2d ago](https://hashnode.com/posts/caching-strategies-explained-cache-aside-vs-write-through-vs-write-back/6af2ad3deab2d7dd582ed003) ### [Saga vs Two-Phase Commit: How Microservices Keep Orders and Payments in Sync](https://scaledojo-engineering.hashnode.dev/saga-vs-two-phase-commit-how-microservices-keep-orders-and-payments-in-sync?utm_source=hashnode&utm_medium=feed) Picture an online store built from separate services. An order service, a payment service, an inventory service and a shipping service each have their own database. A customer clicks "Buy," and four t 5 min read · [scaledojo-engineering.hashnode.dev](https://scaledojo-engineering.hashnode.dev/saga-vs-two-phase-commit-how-microservices-keep-orders-and-payments-in-sync?utm_source=hashnode&utm_medium=feed) [Oct 29](https://hashnode.com/posts/saga-vs-two-phase-commit-how-microservices-keep-orders-and-payments-in-sync/6ae33c0bab891790ab790a0f) ### [Consistent Hashing Explained: Add Servers Without Reshuffling Everything (with Python)](https://scaledojo-engineering.hashnode.dev/consistent-hashing-explained-add-servers-without-reshuffling-everything-with-python?utm_source=hashnode&utm_medium=feed) Imagine you run a distributed cache with four servers. Whenever a request arrives, you need to decide which server should store the corresponding key. A simple solution is to use modulo hashing: serve 10 min read · [scaledojo-engineering.hashnode.dev](https://scaledojo-engineering.hashnode.dev/consistent-hashing-explained-add-servers-without-reshuffling-everything-with-python?utm_source=hashnode&utm_medium=feed) [Oct 28](https://hashnode.com/posts/consistent-hashing-explained-add-servers-without-reshuffling-everything-with-python/6ae1c7d6a1b3059008a5edb9) ### [Chaos Engineering for Beginners: How to Break Your System on Purpose (Safely)](https://scaledojo-engineering.hashnode.dev/chaos-engineering-for-beginners-how-to-break-your-system-on-purpose-safely?utm_source=hashnode&utm_medium=feed) Your system works fine on a normal day. The real question is what happens on a bad one: a server goes down, a dependency slows down, or the network starts dropping packets. You can wait for production 7 min read · [scaledojo-engineering.hashnode.dev](https://scaledojo-engineering.hashnode.dev/chaos-engineering-for-beginners-how-to-break-your-system-on-purpose-safely?utm_source=hashnode&utm_medium=feed) [Oct 26](https://hashnode.com/posts/chaos-engineering-for-beginners-how-to-break-your-system-on-purpose-safely/6adf063ac3b3c8903c0660b0) ### [How to Design a Rate Limiter: Algorithms, Architecture, and System Design Trade-Offs](https://scaledojo-engineering.hashnode.dev/how-to-design-a-rate-limiter-algorithms-architecture-and-system-design-trade-offs?utm_source=hashnode&utm_medium=feed) Imagine your API suddenly receives thousands of requests from a single client. Application servers become overloaded, response times increase, and legitimate users start experiencing failures. A rate 8 min read · [scaledojo-engineering.hashnode.dev](https://scaledojo-engineering.hashnode.dev/how-to-design-a-rate-limiter-algorithms-architecture-and-system-design-trade-offs?utm_source=hashnode&utm_medium=feed) [Oct 23](https://hashnode.com/posts/how-to-design-a-rate-limiter-algorithms-architecture-and-system-design-trade-offs/6adb44141894501c798cebf0)