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).

Add item to basket is a single feature

question here: - if "add item to basket" is a vertical slice - then is "change item quantity in basket", "remove item from basket" etc etc - are these all separate vertical slices? You end up having hundreds of them?

I’d group them in modules/submodules/features. You don't need to have a slice as a module and a flat structure. That wouldn't be maintainable.

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/

From my works, you can check my article on facts and myths about CQRS: event-driven.io/en/cqrs_fact... I think that what I wrote there applies also to Vertical Slices (at least in my understanding). 3/

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