Post

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

3 reposts7 likes

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?

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/

IMO the extremes (and the jokes around them) are also educative - the pitfalls, misuses etc. all the dark side is a must-have on my list - in order to say "I understand" the aspect. Keep on going 🔥 as long as it's technical

I guess we go to the extreme on the vertical slices side (every user action is it's own slice). But we combine vertical slices with a fractal architecture so that the slices can share stuff to keep the code cohesive. For us, this works great. www.planetgeek.ch/2024/09/19/o...

planetgeek.chOnion, Hexagonal, Clean or Fractal Architecture? All of them, and more!!Onion, Hexagonal, Clean, or Fractal Architectures aim to organize how we deal with dependencies in our software architectures. But which one should we choose? After distilling the essence of each appr...

Yes, I think those are orthogonal concepts, and we can mix them into our approaches. For simpler cases, I tend to lean more into vertical slices, just doing basic logic, for more complex domains, I prefer to group and center operations more around the central model.

It's not what I think. It's what I see being done in practice. That's not to say "it's the pattern's fault". It's a very different focal point for the most part, cultivating a model or cranking out vertical slices. People seem to flock to one or the other.