Architecture

A few days ago I attended a small, invite-only tech gathering hosted by Cafe Ertebat. Think of it as a low-key salon: about a couple dozen people, all of them with at least a decade of experience, almost all with shiny titles: CTOs, VPs of Engineering, technical leads, founders. It was the kind of room you’d expect to be intimidating. It wasn’t. And that was the interesting part. Walking into an “Elite” Room I was invited through two friends and colleagues who referred me to the host. That alone set a certain expectation in my head: if this is curated, and everyone is hand-picked, then the conversation is probably going to be sharp, opinionated, and uncomfortably insightful. ...

I was midway through a system-design talk when a familiar question landed: So… is DDD an architecture or a pattern? The room had many .NET folks. Heads tilted. Some smiled the “here we go” smile. Let’s answer it simply, and then go a little deeper; without buzzword gymnastics. A simple definition of DDD Domain-Driven Design (DDD) is a way of designing software by centering everything on the language and rules of the business. It gives you two kinds of tools: ...

Introduction In the ever-evolving landscape of software development, tracking changes to data is a fundamental requirement. Whether for auditing, debugging, compliance, or analytics, maintaining a history of changes enhances transparency and accountability within a system. Two prevalent approaches to capturing these changes are storing a change log and using event sourcing. While they share common goals, they differ significantly in implementation and suitability depending on the system’s needs. This blog post delves into the similarities and differences between change logs and event sourcing, assesses their applicability through practical examples, and provides guidance on choosing the right approach for your system. ...