HomeStackProjExpSysArtArch
Engineering & The Builder's Life

Systems, Craft &
The Human Side.

Deep-dives into distributed systems and architecture, alongside honest writing about the engineering career — imposter syndrome, growth, focus, and what nobody warns you about the job.

5 articles published

All Articles5 total
[01]Engineering LifeFeatured

Nobody Warns You About This Part of Engineering

The gap between what you learn and what real engineering actually demands. On imposter syndrome that doesn't leave, the trap of being the reliable one, what 'senior' really means, and the unwritten rules that separate engineers who grow from engineers who grind.

CareerEngineering LifeGrowthImposter Syndrome
14 min read
[02]System DesignFeatured

Distributed Transactions in Microservices: Why Consistency Becomes Difficult

ACID guarantees hold inside a single database. The moment you split business operations across microservices, you lose the atomicity safety net. This article dissects why distributed consistency is hard, what the industry-standard patterns actually cost, and how to make pragmatic architectural decisions.

Distributed SystemsMicroservicesSAGAConsistency
18 min read
[03]System Design

Two-Phase Commit (2PC): Achieving Atomicity Across Distributed Systems

Two-Phase Commit is the classical protocol for distributed atomic transactions. This article dissects its mechanics, why it fails at scale, the specific failure modes that make it dangerous in microservices, and the precise conditions under which it remains the correct tool.

Distributed Systems2PCConsistencyTransactions
15 min read
[04]System Design

CAP Theorem Explained: The Tradeoffs Behind Distributed Systems

The CAP theorem states that a distributed system can guarantee at most two of three properties: Consistency, Availability, and Partition Tolerance. Understanding what this actually means — and what it doesn't — is fundamental to every architectural decision in distributed systems.

Distributed SystemsCAP TheoremConsistencyAvailability
16 min read
[05]System Design

Understanding the SAGA Pattern: Coordinating Long-Running Transactions

A SAGA replaces a distributed transaction with a sequence of local transactions and compensating operations. This article goes deep on both coordination models, state machine design, isolation trade-offs, and the countermeasures that make SAGAs production-safe.

Distributed SystemsSAGAMicroservicesArchitecture
20 min read

Working on something
worth building?

Open to conversations about distributed systems, backend architecture, or just the realities of a long engineering career.

Get in Touch