Skip to content
Hallway
0:00 / 0:00

#verticalslicearchitecture#csharp#.net

Vertical Slice Architecture Project Setup From Scratch

Milan Jovanović

169K subscribers • 12 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Milan Jovanović

Intermediate. Assumes working knowledge.

92K views3 years ago2 recommendations

Software designSoftware architectureDesign patterns

Milan Jovanović demonstrates how to set up a .NET project from scratch using Vertical Slice Architecture instead of traditional layering.

Get the source code for this video for FREE → the-dotnet-weekly.ck.page/vsa ☄️ Master the Modular Monolith Architecture: bit.ly/3SXlzSt 📌 Accelerate your Clean Architecture skills: bit.ly/3PupkOJ 🚀 Support me on Patreon to access the source code: patreon.com/milanjovanovic Vertical Slice Architecture is an interesting approach to structure your project. Instead of thinking about layers, you try to group components by features. Vertical Slice Architecture has higher cohesion between components, and finding your way around the project is easy. It's not surprising - everything related to a single feature is in one place. Find out how to implement Vertical Slice Architecture in this video. Vertical Slice Architecture milanjovanovic.tech/blog/vertical-slice-architecture Join my weekly .NET newsletter: milanjovanovic.tech Read my Blog here: milanjovanovic.tech/blog Subscribe for more: youtube.com/@MilanJovanovicTech?sub_confirmation=1 Chapters Clean Architecture vs Vertical Slice Architecture Adding the first Vertical Slice - Create Article Installing MediatR to implement use cases Exposing an endpoint for the Vertical Slice Supporting validation with FluentValidation Creating API contracts and adding Mapster Adding the second Vertical Slice - Get Article Grouping components by feature and cohesion

Why it's here

2 people recommend this

What people say. Recommended as a practical guide for setting up and understanding Vertical Slice Architecture in .NET projects.

Moments people linked to

u/Flamyngooin r/dotnet • Recommends

Vertical Slice Architecture and shared functionality Hi all! I started learning and experimenting using Vertical Slice Architecture, and more precisely based on this video: [video I have one question, lets say i have this structure features->auth, and there are 2 endpoints for generating JWT tokens for example, GenerateTokenFromGoogle,GenerateTokenFromCredentials etc. etc. Each of them has some functionality but at the end of the day they create a token so we have a generateJWT method, as each of the features use it...where do i put it. In a shared folder? Service folder? I thought the VSA should let you omit services, maybe there is some better way i am missing
12View on Reddit

u/MeringueFit201in r/FlutterDev • Recommends

On “flutter clean architecture ”

…ver call an implementation outside your logic stuff, only the interfaces). Dart makes that one really difficult, since it has 0 introspection capabilities so, basically, you must rely on some weak service locator such as `InheritedWidget` or `get_it`. The rest is only a rearrangement of those things (see, for example, Vertical Slice Architecture: link to this video and link to this video There are also a lot of patterns that are VERY VERY VERY useful to Flutter and aren't directly in CA: Mediator Pattern and MVVM are a must for Flutter (to stop this nonsense unneeded shit JavaScript statement management libraries)…
5View on Reddit