Vertical Slice Architecture (Jimmy Bogard)

Рет қаралды 8,264

Күн бұрын

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.
ABOUT JIMMY
Jimmy is the creator and maintainer of the popular OSS libraries AutoMapper and MediatR. Jimmy is an independent software consultant based in Austin, TX. Jimmy has received the "Microsoft Most Valuable Professional" (MVP) award every year since 2009.
- LinkedIn: / jimmybogard
- Twitter: x.com/jbogard
- GitHub: github.com/jbogard
- Blog: www.jimmybogard.com/
TECH EXCELLENCE
- Subscribe to our KZfaq channel / @techexcellence
- Join our Meetup Group www.meetup.com/techexcellence
- Follow us on LinkedIn / techexcellenceio
- Follow us on Twitter / techexcellence_
- Join our Discord Community / discord
TIMESTAMPS
0:00 Intro
1:30 Architecture (Traditional, DDD...)
17:39 CQRS
20:40 Vertical Slice Architecture
46:19 Red Green Refactor
1:00:53 Key Takeways
1:03:52 Live Q&A
#refactoring #softwareengineering #architecture #softwarearchitecture #techexcellence

Пікірлер: 9

@Cerebradoa 2 ай бұрын

I've discovered the same architecture, in the same way you did. And, by experience, do not reuse code between handlers. There is nothing wrong on having copied/pasted code. Keep in mind modifications will come per feature, so, probably, this code will need to evolve independently, and the duplicated code will not be duplicated any more.

@ianhamilton8376 2 ай бұрын

This architecture has been around for over 20 years in the modular monolith/modular client. What this video really shows is how little most developers really understand about software architecture and how poorly it seems to have been taught for a long time.

@programuoki-lt1465 3 күн бұрын

Agree and then populating all medias with good clean architecture courses :) I feel same aspect Divide and Conquer only different context.

@weifengmao 2 ай бұрын

The biggest advantages of using vertical slice architecture is FEWER MERGE CONFLICTS!

@m1croN1337 5 ай бұрын

Great presentation! Jimmy mentions on 59:00, that they've built a "Unit of work" for a data storage that does not support it out of the box. Are there any examples available online?

@devaliero-3d597 2 ай бұрын

I used already Vertical Slice architecture at the beginning of my career, it was then known as Big Ball of Mud

@PaulSebastianM 3 ай бұрын

He didn't invent VSA. He formalized it. VSA is described in the Clean Architecture book by that old guy, uncle Bob or something like that. 😅 Joke aside I don't know for sure if it's even older than that or who's described the idea first.