--- title: "#systemdesign articles | Hashnode" description: "Explore 154 articles tagged #systemdesign on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/systemdesign" --- Tag # #systemdesign 154 posts · 23 followers [CheckNumber](https://hashnode.com/@checknumber) · [6d ago](https://hashnode.com/posts/the-identity-resolution-paradox-handling-shared-phone-numbers-in-crm-architectures/6aec5bd39c3292e2a5fe82c6) ### [The Identity Resolution Paradox: Handling Shared Phone Numbers in CRM Architectures](https://checknumberofficial.hashnode.dev/the-identity-resolution-paradox-handling-shared-phone-numbers-in-crm-architectures?utm_source=hashnode&utm_medium=feed) Merging contacts based on a shared phone number often destroys critical relationship metadata; developers should implement a 'household' or 'entity' abstraction layer instead of destructive deduplication. 6 min read · [checknumberofficial.hashnode.dev](https://checknumberofficial.hashnode.dev/the-identity-resolution-paradox-handling-shared-phone-numbers-in-crm-architectures?utm_source=hashnode&utm_medium=feed) [TgValidator](https://hashnode.com/@tgvalidator) · [6d ago](https://hashnode.com/posts/managing-identity-drift-in-messaging-based-contact-systems/6aec5495031e0eb52cd547e4) ### [Managing Identity Drift in Messaging-Based Contact Systems](https://tgvalidator.hashnode.dev/managing-identity-drift-in-messaging-based-contact-systems?utm_source=hashnode&utm_medium=feed) When user-controlled identifiers like usernames change, automated systems often break; the solution is to implement a reconciliation layer that flags mismatches for manual review rather than performing destructive updates. 5 min read · [tgvalidator.hashnode.dev](https://tgvalidator.hashnode.dev/managing-identity-drift-in-messaging-based-contact-systems?utm_source=hashnode&utm_medium=feed) [ZyVOP](https://hashnode.com/@zyvop) · [Nov 4](https://hashnode.com/posts/redis-caching-patterns-cache-aside-write-through-and-the-stampede-problem-ul6qw/6aeabd4377469c96b4b8dfb1) ### [Redis Caching Patterns: Cache-Aside, Write-Through and the Stampede Problem](https://blog.zyvop.com/redis-caching-patterns-cache-aside-write-through-and-the-stampede-problem-ul6qw?utm_source=hashnode&utm_medium=feed) How common Redis caching patterns work, where they fail, and how to prevent cache stampedes, with runnable Python examples and reproducible simulations. 26 min read · [blog.zyvop.com](https://blog.zyvop.com/redis-caching-patterns-cache-aside-write-through-and-the-stampede-problem-ul6qw?utm_source=hashnode&utm_medium=feed) [Doogal Simpson](https://hashnode.com/@doogal) · [Oct 31](https://hashnode.com/posts/transactional-outbox-pattern/6ae6045125420ae25c93dab0) ### [Transactional Outbox Pattern: Fix Dual Writes](https://doogal.dev/transactional-outbox-pattern?utm_source=hashnode&utm_medium=feed) Fix distributed dual-write inconsistencies in microservices using the Transactional Outbox Pattern to guarantee reliable, at-least-once event delivery. 4 min read · [doogal.dev](https://doogal.dev/transactional-outbox-pattern?utm_source=hashnode&utm_medium=feed) [TgValidator](https://hashnode.com/@tgvalidator) · [Oct 29](https://hashnode.com/posts/architecting-stable-identity-mapping-for-messaging-integrations/6ae31a56f7fb9eda86d425c7) ### [Architecting Stable Identity Mapping for Messaging Integrations](https://tgvalidator.hashnode.dev/architecting-stable-identity-mapping-for-messaging-integrations?utm_source=hashnode&utm_medium=feed) Relying on mutable identifiers like usernames or phone numbers for database keys leads to data fragmentation; developers must prioritize immutable numeric identifiers for long-term state management. 6 min read · [tgvalidator.hashnode.dev](https://tgvalidator.hashnode.dev/architecting-stable-identity-mapping-for-messaging-integrations?utm_source=hashnode&utm_medium=feed) [ZyVOP](https://hashnode.com/@zyvop) · [Oct 29](https://hashnode.com/posts/caching-strategies-compared-cache-aside-write-through-and-write-behind-7t4z2/6ae2e79e8c9057215d218795) ### [Caching Strategies Compared: Cache-Aside, Write-Through, and Write-Behind](https://blog.zyvop.com/caching-strategies-compared-cache-aside-write-through-and-write-behind-7t4z2?utm_source=hashnode&utm_medium=feed) How each pattern moves data between your app, cache, and database, and how to pick the right one for your read/write mix. 5 min read · [blog.zyvop.com](https://blog.zyvop.com/caching-strategies-compared-cache-aside-write-through-and-write-behind-7t4z2?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/caching-strategies-compared-cache-aside-write-through-and-write-behind-7t4z2/6ae2e79e8c9057215d218795) [ZyVOP](https://hashnode.com/@zyvop) · [Oct 26](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc) ### [Rate Limiting Algorithms: How to Protect Your API Without Annoying Your Users](https://blog.zyvop.com/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e?utm_source=hashnode&utm_medium=feed) How fixed windows, sliding windows, token buckets and leaky buckets work, where each one breaks, and how to pick the right one for your API. 11 min read · [blog.zyvop.com](https://blog.zyvop.com/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e?utm_source=hashnode&utm_medium=feed) [10](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc) [Dipen Shah](https://hashnode.com/@techEcho) · [Oct 25](https://hashnode.com/posts/the-dilemma-experiment-episode-5-spatial-networks-topologies/6addf06059d156786ccd3ed7) ### [The Fortress of Geography: How Spatial Networks and 2D Grids Shield Cooperation from Parasites](https://techecho.hashnode.dev/the-dilemma-experiment-episode-5-spatial-networks-topologies?utm_source=hashnode&utm_medium=feed) The Dilemma Experiment — Episode 5: Spatial Networks & Network Topologies 8 min read · [techecho.hashnode.dev](https://techecho.hashnode.dev/the-dilemma-experiment-episode-5-spatial-networks-topologies?utm_source=hashnode&utm_medium=feed) [Doogal Simpson](https://hashnode.com/@doogal) · [Oct 24](https://hashnode.com/posts/netflix-system-design-aws-open-connect/6adca3cf2c61dacc22b80627) ### [How Netflix Architecture Works: AWS & Open Connect CDN](https://doogal.dev/netflix-system-design-aws-open-connect?utm_source=hashnode&utm_medium=feed) Explore Netflix's hybrid architecture: how AWS handles control plane logic while Open Connect Appliances pre-cache video streams inside ISP networks. 4 min read · [doogal.dev](https://doogal.dev/netflix-system-design-aws-open-connect?utm_source=hashnode&utm_medium=feed) [Anonymous](https://hashnode.com/@imsam) · [Oct 23](https://hashnode.com/posts/your-system-design-looks-fine-on-a-whiteboard-until-traffic-hits/6adb15b63bd2d77f11cadcc2) ### [Your System Design Looks Fine on a Whiteboard. Until Traffic Hits.](https://stackmonkey.hashnode.dev/your-system-design-looks-fine-on-a-whiteboard-until-traffic-hits?utm_source=hashnode&utm_medium=feed) Explore how traffic spikes, cache failures and database bottlenecks affect system design, with practical examples and hands-on experiments. 4 min read · [stackmonkey.hashnode.dev](https://stackmonkey.hashnode.dev/your-system-design-looks-fine-on-a-whiteboard-until-traffic-hits?utm_source=hashnode&utm_medium=feed)