Dayul's Tech Blog
Management informs. Engineering decides.
Code is strategy. Architecture has a reason.
Engineering has no absolute answers, only optimal trade-offs.
Code is strategy. Architecture has a reason.
Engineering has no absolute answers, only optimal trade-offs.
📘 Track 1. CS Fundamentals
Section titled “📘 Track 1. CS Fundamentals”- Operating System Series (3)
- Network Series (5)
- Database Series (6)
⚙️ Track 2. Problem Solving — Minichat Trade-offs
Section titled “⚙️ Track 2. Problem Solving — Minichat Trade-offs”- Choosing Lua Script Over Distributed Lock
- When Kafka Ordering Matters and When It Doesn’t
- Choosing a Read Strategy Under Replication Lag
- Why the Same Redis Failure Needs Different Responses
- Choosing an ID Strategy for Distributed Systems
- Choosing Target Routing Over Broadcast
- Choosing Server-Level Bulk Relay Over Per-User Processing
🧪 Track 3. System Validation — Minichat Load & Fault Injection Experiments
Section titled “🧪 Track 3. System Validation — Minichat Load & Fault Injection Experiments”