Skip to content
0:00 / 0:00

#verticalslicearchitecture#cqrs#ddd

Vertical Slice Architecture - Jimmy Bogard

NDC Conferences

230K subscribers • 68 videos on Hallway • Conference channel

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Jimmy Bogard
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

112K views8 years ago1 recommendation

Software designSoftware architectureDesign patterns

Jimmy Bogard presents an alternative to traditional layered architecture, explaining how to organize applications around vertical slices of functionality.

Moving from a layered architecture to a vertical slice architecture can be a bit daunting. We remove abstractions, complex structures, and focus building on the axis of change, then what's next? What new structures, patterns, and policies will need to be introduced in this style of architecture? How will we deal with common business functionality, and where do concepts like CQRS and DDD fit in? In this session, we'll introduce the idea of vertical slice architectures, and dive into the patterns, tools, and techniques used with slices. We'll also cover how you can fit vertical slices into different kinds of systems, from desktop, SPA, and normal MVC applications. Finally, we'll look at some of the new challenges that come with slices and layers, and how a different approach provides a much more maintainable end result. NDC Conferences ndcsydney.com ndcconferences.com

Why it's here

1 person recommends this

What people say. Recommended as a key resource for understanding Vertical Slice Architecture and how it compares to Clean or Onion Architecture.

u/pdevito3in r/dotnet • Recommends

# Choosing Between using Clean/Onion or Vertical Slice Architecture for Enterprise Apps in .NET So I did a lot of research last year on how I should be organizing my apps and landed on Clean/Onion as one of the best if not *the* gold standard of how one should be organizing maintainable and complex apps. I read books and blogs, checked out the eShop projects, saw jason taylor and steve smith's example projects, and tried a few POCs myself. It worked well and I liked it. I even made a tool that can scaffold out a Clean web api that works pretty nicely. Regardless of the below, I can pretty definitely say that a Clean organization is a solid approach. With that said, I came across the [Vert…

u/pdevito3in r/softwarearchitecture • Mentions

On “Books to get better at software design/architecture?”

I’d say my apps have become significantly more maintainable ever since I started using vertical slice architecture to organize my apps and using domain rich entities. As far as books that facilitate the rich domain portion: - Refactoring: Improving the Design of Existing Code (2nd Edition) (Addison-Wesley Signature Series (Fowler)) https://www.amazon.com/dp/0134757599/ref=cm_sw_r_cp_api_glt_fabc_G6FWM4S7JE9SRKP7PFJ7?_encoding=UTF8&psc=1 - Refactoring to Patterns https://www.amazon.com/dp/0321213351/ref=cm_sw_r_cp_api_glt_fabc_HCE3N5W8NREA08CSMC6E - Patterns of Enterprise Application Architecture https://www.amazon.com/dp/0321127420/ref=cm_sw_r_cp_api_glt_fabc_SBV30RTWSTGHMFSG6H75