What Does “Consistent” Actually Mean? ACID, BASE, and Correctness
Understand ACID vs BASE through a B2B payment workflow covering transactions, isolation, idempotency, outbox patterns, retries, and eventual consistency.
Article archiveEngineering ideas,
Engineering ideas,
decisions and field notes.
Practical writing drawn from real systems, product constraints, architecture decisions, and lessons from implementation.
Published notes
Browse by topic7 articles
Relational or NoSQL? Choosing a Database From Your System’s Requirements
Choosing a database is not simply a contest between SQL and NoSQL. This guide evaluates relationships, invariants, access patterns, failure tolerance, and operational cost through the architecture of a B2B invoicing platform.
Designing a Reliable AI Customer-Support Workflow
Learn how to design an AI-assisted customer-support workflow that can safely investigate duplicate charges, apply policy, issue refunds, recover from failures, and maintain a complete audit trail.
An AI Feature Is Not an AI System
A production AI assistant is not defined by the model it calls, but by the controls, context, validation and recovery mechanisms surrounding that model.
What Happens After a Message Enters the Queue?
Publishing a message is only the beginning. This article explains how brokers route messages, how failed work is retried, why poison messages require dead-letter queues, and when priority improves—or destabilizes—a processing pipeline.
Message Queues: The Boundary Between Receiving Work and Processing It
Message queues separate accepting work from completing it. This article explains producers, consumers, acknowledgements, delivery guarantees, backpressure, and the architectural problems queues are designed to solv
Role-Based Access Control Is a Data-Modelling Problem
Authorization isn't just about who you are. It’s about how your data is shaped. Here is why secure systems start at the schema level.