The Command Context Consistency Principle
How Event Stores and Relational Databases Guard Business Decisions
Topic
Software Architecture
A collection of 32 issues
Why Your Software Cannot Explain Its Business Decisions
Make the path from command to outcome explicit in the architecture. How you store state, relational or event-sourced, is a separate decision.
Thinking in Events
Separating the Modeling of What Happened from the Decision of How to Store It
Why the Domain Is Defined by Domain Capabilities, Not Object Models
Additive Domain Evolution Through Autonomous Capabilities
Request Processing Units and Reactors
Decoupling User Interactions from Internal Domain Capabilities
Functional Core / Imperative Shell for Agentic Coding
How Repository Structure, Feature Slices, and Project-Level Skills Guide Coding Agents Toward Self-Contained Features
Why Simple Changes Rarely Stay Simple
How software systems become resistant to simple change
Building a Durable Telemetry Ingestion Pipeline with Rust and NATS JetStream
Why Direct-to-Database Ingestion Fails at Scale and What Actually Works
Beyond Enterprise OOP: Building Clear, Composable Systems with PostgreSQL and Rust
PostgreSQL Guards the Facts, Rust Defines Intent, and Clarity Scales with the System
Beyond Static Models: Behavior-First Design for Changing Domains
Why Your ERD Is Not the Domain and How Events Make Systems Explainable