Tag feed

#system-architecture

1,252 posts1,377 followers

Trending tags this week

RLRudraksh Laddharudrakshladdha.hashnode.dev

Core Building Blocks — 12 Fundamental Concepts (Part 1)

4h ago · 2 min read · Each concept below follows the same structure: What it is → Why it exists → When to use → When NOT to use → Trade-offs → Real examples → Diagram → Beginner mistakes. The 12 Concept are : Requiremen

Join discussion

ZTZeyad Tarekzeyadtarekk.hashnode.dev

0

Backend Communication Patterns Explained

1d ago · 13 min read · From Request/Response to Event-Driven Systems Modern backend systems rarely rely on a single communication model. A simple CRUD API may work perfectly with request/response communication, while a chat

Join discussion

RLRudraksh Laddharudrakshladdha.hashnode.dev

0

System Design Thinking Framework — 7-Step Engine

1d ago · 6 min read · Purpose: This is your universal problem-solving engine. Apply these 7 steps to EVERY system design question, in this exact order. Never skip steps. Never reorder them. The 7-Step Framework Step 1 —

Join discussion

RRicharichak.hashnode.dev

0

List Virtualisation — Rendering 10,000 Rows Without Killing the Browser

3d ago · 8 min read · Hey everyone, Richa here! 👋 Day 23. Story time. I once got a bug report that said: "the transactions page takes 8 seconds to load and then freezes when you scroll." The page was rendering a table wi

Join discussion

RRicharichak.hashnode.dev

0

Code Splitting and Lazy Loading — React.lazy, Suspense, and Dynamic Imports

4d ago · 9 min read · Hey everyone, Richa here! 👋 Day 22. And today we talk about one of the most impactful performance wins available in any React app — and one of the most underused. Code splitting. Here's the thing ab

Join discussion

MMMainStay Marketingmainstay.hashnode.dev

0

System Ownership

6d ago · 1 min read · When no one owns a system, everyone works around it. Decisions slow down, issues remain unresolved, and the system drifts away from business needs. Ownership is not a label. It is continuous accountab

Join discussion

SGShashinoor Ghimireshashinoorghimire.com.np

0

Event Driven System using Database Write Ahead Log and Change Data Capture

6d ago · 8 min read · 💡 TLDR: Polling is wasteful and can't give you true real-time delivery. Emitting events directly from application code is fragile — a partial failure leaves your database and broker out of sync. WAL-

Join discussion

RRicharichak.hashnode.dev

0

Monorepo Basics — When and Why Teams Move to Monorepos

May 12 · 7 min read · Hey everyone, Richa here! 👋 Day 20. Last day of Week 4. 🎉 And today we zoom out from component-level architecture to something that affects the whole engineering org. Monorepos. This is one of t

Join discussion

DCDanny Crastoblog.danwald.me

0

Design a key-value store

May 10 · 3 min read · A Key-Value store is just a hash table, until it isn't. At scale, keys shard across servers via consistent hashing and the CAP Theorem becomes the constraint you design around. CAP Theorem Consistency

Join discussion

MPMadhu Prashanth Kannanenterpriseaisignals.hashnode.dev

0

When workflows become automated, where does innovation go?

May 9 · 3 min read · A large amount of practical engineering innovation historically emerged from everyday operational friction. Debugging failures. Scaling systems. Working around limitations. Repeated exposure to

Join discussion

#system-architecture

Search Hashnode

#system-architecture

Trending tags this week

Core Building Blocks — 12 Fundamental Concepts (Part 1)

Backend Communication Patterns Explained

System Design Thinking Framework — 7-Step Engine

List Virtualisation — Rendering 10,000 Rows Without Killing the Browser

Code Splitting and Lazy Loading — React.lazy, Suspense, and Dynamic Imports

System Ownership

Event Driven System using Database Write Ahead Log and Change Data Capture

Monorepo Basics — When and Why Teams Move to Monorepos

Design a key-value store

When workflows become automated, where does innovation go?