Skip to content
0:00 / 0:00

#verticalslicearchitecture#cleanarchitecture#dotnet

Designing for change with Vertical Slice Architecture - Chris Sainty - NDC London 2024

NDC Conferences

230K subscribers • 110 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Chris Sainty
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

27K views2 years ago2 recommendations

Software designWeb developmentSoftware architectureDesign patterns

Chris Sainty discusses the limitations of traditional layered architectures and demonstrates how Vertical Slice Architecture helps teams build maintainable, change-tolerant systems.

This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper Attend the next NDC conference near you: ndcconferences.com ndclondon.com/ Subscribe to our YouTube channel and learn every day: / @NDC Follow our Social Media! facebook.com/ndcconferences twitter.com/NDC_Conferences instagram.com/ndc_conferences/ #dotnet #architecture #agile #ddd #microservices #software #apps While traditional layered architectures have held their ground for years—structing applications into recognisable tiers such as “presentation”, “business logic”, and “data”. Are they really suited to the demands of modern software development? Teams are being asked to move faster and faster as well as be able to change direction quickly as customer needs change. And what happens when a product hits success and needs to scale, fast! Do these architectures make it easy for apps to scale and new developers to get up to speed and be productive quickly? Essentially, do these architectures allow teams to build for change? The one constant in our industry. In this talk, we’re going to look at an alternative way to build applications using vertical slice architecture (VSA). You’ll learn what VSA is and how it differs from the layered approach. We’ll cover it’s key advantages and how it can help you, or your teams, build better software, faster. We’ll also talk about some common misconceptions of the architecture as well as trade-offs when choosing it.

Why it's here

2 people recommend this, 1 disputes it

What people say. Recommended for learning modular monoliths and vertical slice architecture, though some developers debate its impact on code duplication.

u/RussianHacker1011101in r/dotnet • Recommends

On “Any good resources for monolithic software architecture?”

First of all, thank you for trying out monolithic software architecture. I wish this was the default choice. I taught myself about modular monoliths and vertical slice architecure basically via youtube. Here's a list of videos that got me up to speed on the concepts: - Visual Studio Toolbox Live - Building a Modular Monolith - [Designing for change with Vertical Slice Architecture - Chris Sainty - NDC London 2024] - Modularizing the Monolith - Jimmy Bogard - NDC Oslo 2024 It's actually an extremely simple way of designing softare that really requires minimal architecutre. As you implement vertical slices, you'll gradually understand it more. This is a summary of what I've learned: Let…

u/Eagle157in r/dotnet • Recommends

On “.Net architecture”

Check out Chris Sainty's session from NDC on YouTube link to this video

u/st4rdr0idin r/dotnet • Disputes

On “What are your experience with Clean Architecture vs Vertical slice architecture”

Vertical slicing as per this talk is caving up to pressure and imprinting developer work units into the code with no effort, at the cost of low cohesion (many slices are related or even identical) and code repetition. The "no sharing" policy is just being too lazy to understand what already exist in the codebase, and it becomes impossible when you need to e.g.: modify a screen that belongs to a past feature (slice). If however slices are DDD's bounded contexts then that has my respects.

u/MathematicianSome289in r/Frontend • Mentions

On “What is your favorite architecture on react?”

All due respect but this is the exact opposite of what I would recommend. This is a “horizontal” architecture where code is organized by _technical_ concern. This leads to tight coupling. I recommend a “vertical slice” architecture where code is organized by feature. Within feature slices it’s ok to organize by concern. This way, if you need to port a feature, you can. Please consider watching this talk to see more why horizontal architectures are not optimized for change