Vertical Slices in software architecture are pictured right now as the best thing since sliced bread. I won’t try to hide that, like it. I've written about CQRS and Vertical Slices over the years - how to slice the codebase effectively, shown examples, and explained why generic doesn't mean simple, yet…I still get questions about Vertical Slices Architecture (VSA). After a recent Discord discussion, I want to share some additional thoughts on how I see Vertical Slices Architecture, how it...| www.architecture-weekly.com
...but also for building Adaptive Streaming Pipelines. I wrote today on how building event-driven pipeline lead me to writing my own compiler. Oh well, small one, simple one, but still. Learn on surprising places besides programming languages when compiling happens and helps your apps!| Architecture Weekly
People claim they get 10x productivity boosts with AI coding tools. After my recent experiments with Claude Code, I'm starting to think we're not using these tools the same way. Or that they’re just lying. Or both. See my story, and learn why you should not be like Gabriel!| www.architecture-weekly.com
The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions. Lets discuss the dual license movement, what do they mean? All of that based on the reasearch I've done for my OSS projects.| Architecture Weekly
This week I want to tell you about the design proposal for the workflow engine. I want to provide the lightweight way to handle business processes in durable, observable and resilient way. Check what I brewed and tell me your thoughts!| www.architecture-weekly.com
Ordering or performance, pick one wisely! Selecting both is impossible. At least in distributed systems, aiming to handle a bigger load. Why? We discussed this in detail today, taking PostgreSQL, MongoDB, and Kafka, and analysing the tradeoffs they chose!| Architecture Weekly
Let's follow up today on fighting with eventual consistency, causal consistency and how predictable ids can help you with that. We'll take on my real project: decoupling file upload from linking it in various places in the application.| www.architecture-weekly.com
What if we could enable modules to communicate without knowing about each other's existence? What if a payment module could process requests from any source without being programmed to handle specific scenarios? We’ll explore today how predictable identifiers, specifically Uniform Resource Names (URNs), provide an elegant solution to this challenge.By structuring identifiers in a predictable format, we enable infrastructure-level routing and correlation without module-specific logic.| Architecture Weekly
Watch a jazz quartet improvise, and you might think they're making it up as they go. They're not. Every riff builds on practised scales and learned patterns. The constraints don't stifle creativity—they make it work. The same goes for software modelling. Before we get into the chaos of group exercise, we need to have the frame and material to improvise.| www.architecture-weekly.com
In 2016, the Kafka team faced a problem that illustrates a fundamental challenge in distributed systems design: their users needed query capabilities that the original design wasn't capable of. They had to add secondary indexing to enable that. Read more to learn what that is and how that helps specialised storages to extend their capabilities.| Architecture Weekly
Is QA role dead? I've seen that popping in socials. Yet another GenAI victim? This conversation has been going in circles for years, long before AI became everyone's favourite scapegoat. I think that the real question isn't whether AI will replace testers. It's whether we've ever understood what good testing looks like. And how's that read more inside on my thought about QA role!| Architecture Weekly
Today I'm continuing topic of removability and residuals explaining how defining killer feautres is essential to understand how long our software will need to run. This is crucial for not maintaining part of our systems that are not giving a benefit to us and our users.| www.architecture-weekly.com
Today, I'm bringing you Barry O'Reilly's Residuality Theory, one of the most brainwashing approaches to software architecture I've seen in recent years. Check out my notes and findings on how and why you should consider it in your regular design practice.| Architecture Weekly
While teams naturally focus on mapping out those orange event sticky notes (the backbone of any EventStorming session), they often underestimate the power of two critical elements: Hot Spots and Notes.What I value most about Hot Spots and Notes isn't just how they improve workshops - it's how they change team culture around uncertainty.In technical discussions, we often feel pressure to know everything immediately. Hot Spots create permission to say, "I don't know yet" while still making prog...| www.architecture-weekly.com
Occasionally, I'm asked how to get to conferences (especially the bigger ones), I wrote my hints on how to get to speak there, if you want to. Can't guarantee that they will work for you, but they worked somehow for me.| Architecture Weekly
Should you learn multiple languages or be a specialist in one? Should we be adding a new language to our project right after it makes sense from technical perspective? The answer is as always: it depends. Read more to know my take on what.| www.architecture-weekly.com
Have you heard a surgeon say, "I won't sterilise my tools, as patient won't let me"? I didn't, but I heard, multiple times, "Business won't let us add unit tests." Let's discuss how real this phrase is. Is it about business or about ourselves trying to run away from accountability?| Architecture Weekly
Object-oriented or relational? Why not both? Let's look on PostgreSQL JSONB column type and how it can help you to deliver your applications faster. We dived into how it's stored, when and why it can be as performant as regular approach, and cases when we need to do tradeoffs.| www.architecture-weekly.com
Pendulum swung back! Now The "modular monolith first" is the best advice. But is it? It sounds great in theory but can fall short in practice.In practice, too often: module boundaries erode, resource isolation is absent, and that promised "easy split" rarely happens. Also, ease of deployment is not so easy, as CI/CD tooling is not existing or absent. Read more in the recent article!| Architecture Weekly
JavaScript is slow!!! You could get that from the announcement with a 10x performance increase after migrating the TypeScript compiler to Go. The real story? Node.js works well at I/O but struggles with CPU-intensive tasks like compilation. Read more to learn in detail why and what you can learn from it for your systems design!| www.architecture-weekly.com
My lessons learned, dos and donts from breaking down monoliths. I gathered my experience on what to do before even starting. I explained hy defining real business metrics is critical and why you should assume that many Monoliths parts will stay. Of course I mentioned the Strangler Fig pattern, but went further than that!| www.architecture-weekly.com
This week let me share a weird thought I got after landing for a few hours in the hospital. How do we know that we know? How do we don't kno what we don't know? Don't worry, it won't be gibberish, but mind exercise that can be helpful also in your engineering work.| www.architecture-weekly.com