Skip to content
Hallway
0:00 / 0:00

#verticalslicearchitecture#solid#cqrs

Øredev 2016 - Jimmy Bogard - SOLID Architecture in Slices not Layers

Øredev Conference

3.4K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 3 people: 3 in engineering communities.
  • A classic. People kept recommending it from 2017 to 2023.
  • Presented by Jimmy Bogard, creator of MediatR
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

10K views9 years ago3 recommendations

Software designSoftware architectureDesign patterns

Jimmy Bogard argues against traditional layered architectures and explains how to build systems using vertical slices instead.

Want to watch more videos about Methodology? Click here: vimeo.com/album/4414351 For too long we've lived under the tyranny of n-tier architectures. Building systems with complicated abstractions, needless indirection and more mocks in our tests than a comedy special. But there is a better way - thinking in terms of architectures of vertical slices instead horizontal layers. Once we embrace slices over layers, we open ourselves to a new, simpler architecture, changing how we build, organize and deploy systems. Read more: oredev.org/2016/sessions/solid-architecture-in-slices-not-layers Connect with us! Twitter: twitter.com/oredev Facebook: facebook.com/oredev Instagram: instagram.com/oredev Vimeo: vimeo.com/oredev

Why it's here

3 people recommend this

What people say. Recommended as a great explanation of vertical slice architecture and CQRS over traditional layered design.

u/ninjisin r/dotnet • Recommends

On “Is MVC still the right choice for me - Architectural advice?”

This sounds like your best approach. Take all of your business logic and slowly migrate it into another solution that becomes your API. Now your code-behind files will only have the logic needed to call into your API and handle the result. I second the use of CQRS and I would recommend looking at breaking up your implementation into vertical slices/features vs. the traditional n-tiered approach. You might struggle with code duplication for a little while when doing this, but once you have several features online you can start looking at refactoring common pieces out. Jimmy Bogard has done a couple talks on this. If you are willing to jump on the bleeding edge a bit, Razor Pages could…
7View on Reddit

u/CalvinRin r/dotnet • Recommends

On “ASP MVC - recommended do's and don'ts?”

I'm a fan of this architecture link to this video Also it depends what you mean for the cloud, if you just want to spin up a VM and shove the file on their then probably not. If you want to take advantage of cloud native tools then I recommend you look at the 12 Factor App. https://12factor.net/ Also unless you find it doesn't work for you I recommend you use the default IoC that comes with ASP .Net Core, it should work fairly well for your purposes.
3View on Reddit

u/Transcender49in r/dotnet • Recommends

On “Vertical Slice Architecture and shared functionality”

I am unable to answer yoyr question as i really did not learn *yet* the Vertical Slices architecture but i just wanted to drop this video here
3View on Reddit