Post

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

Vertical Slice is a single feature, bounded context is a whole module (so can be a group of vertical slices).

How granular a feature is?

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/

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/

Yeah for me the slice was tied to use cases which are tied to user actions. In a web app this would be a single route with all HTTP methods

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