Post

Tomasz Ducin
@ducin.dev

Fellow #DDD folks out there, Can someone explain to me what is a _practical_ difference between a vertical slice and a bounded context?

Oskar Dudycz
@oskardudycz.bsky.social

For me Vertical Slice Architecture is rebranded CQRS where you slice your applications by behaviour top down. Having that I’d consider a slice per task. Which usually mean a single command/event handling (but can be more). That’s also aligned with task-based UI concept. 1/

Oskar Dudycz
@oskardudycz.bsky.social

I always like to go to the source, so author work, in this case @jimmybogard.com articles and talks: - www.jimmybogard.com/vertical-sli... - www.youtube.com/watch?v=oAoa... That's usually the best way to understand origins. 2/

jimmybogard.comVertical Slice ArchitectureMany years back, we started on a new, long term project, and to start off with, we built the architecture around an onion architecture. Within a couple of months, the cracks started to show around thi...
Tomasz Ducin
@ducin.dev

question: wouldn't it be - technically - more like the following? Considering that a slice could live in multiple places in parallel (shared database - to some extent at least, separate UI codebase, etc.) 1/2

0 reposts0 likes

Jimmy Bogard
@jimmybogard.com

Things are shared when they need to be shared, and this is usually the DB, its data model in code, and parts of the UI like templates/layouts etc. The goal is not “shared nothing” but “share what needs to be”

Tomasz Ducin
@ducin.dev

My understanding is that the main point is to make each slice autonomous. And cohesive. And since db/be/fe are separate units (sep. deploys, sep. servers, whatever) they can't be really treated as a unit universally. Logically - yes. Deployment-wise - no, or at least it depends on many factors 2/2