Clean Architecture with ASP.NET Core 3.0 • Jason Taylor • GOTO 2019

This presentation was recorded at GOTO Copenhagen 2019. #GOTOcon #GOTOcph

Jason Taylor - Solution Architect at SSW

ABSTRACT
The explosive growth of web frameworks and the demands of users have changed the approach to building web applications. Many challenges exist, and getting started can be a daunting prospect. Let's change that now.
This talk provides practical guidance and recommendations. We will cover architecture, technologies, tools, and frameworks. We will examine strategies for organizing your projects, folders and files. We will design a system that is simple to build and maintain - all the way from development to production. You leave this talk inspired and prepared to take your enterprise application development [...]

Download slides and read the full abstract here:

#SoftwareArchitecture #dotNET #Programming #CSharp #CSharpdotNET

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[FH]

Domain layer - 8:34 key points 16:37
Application layer - 17:03 key points 31:39
Infrastructure layer - 32:07 key points 41:25

[Noceo]

As much as I like software architecture, it often tends to get very fuzzy and abstract, when spoken about. Especially for newcomers (like myself). Therefore it's so nice to see a presentation with a lot of concrete examples and actual code. Great job!

[brianwells]

If this had been recorded in 2020, more than a few audience members would have fled the room when Jason kept coughing.


Joking aside, this is a fabulous presentation. Thanks!

[sebastianbergman]

I did exactly this a couple of years back while modernizing an old webforms application, step by step! Awesome that there is new stuff on the topic coming out still. Tip for new comers is reading up on what Jimmy bogard has been blogging about for years, who Jason mentions as one of the disagreeing experts 😅 nice stuff!

[malehernandez]

I've been playing with this template for a while and now I'm getting the whole team up to a real product based on it. It has a very solid foundation, and it's a very approachable implementation.

[sotsch]

This is simply amazing! it shows how easy it is to make architecture clean (in terms of uncle bobs definition) and maximal reusable

[erril]

Thank you very much Jason. I really like Clean Architecture and your example solution is very straight forward and easy to understand. Only 1 thing I would not use: Automapper. I don't like Automapper because it hides references and increases in most cases the code reading time. I think most people believe that Automapper saves development time, but its actually the opposite. When I refactor code or implement new functionalities and I don't have the references which would tell me where all those properties are in use, I would have to constantly look through the AutoMapper mapping profiles from each type which is involved and try to figure out what is going where and what might break if I change a property, because the compiler wont tell me due to the fact that Automapper is doing everything during runtime with reflection, but during development time I don't get any help. That costs much more time than the time you maybe saving when writing the code. And I haven't even mentioned other problems which Automapper is causing like misleading of static analysis. If you want to shrink writing time, then look rather into the Visual Studio extension MappingGenerator on GitHub ;)

[AbhishekSingh-kyud]

Awesome!! Really loved the no fuss, simplistic, to the point explanation❤

[craigmunday]

Excellent talk and a really nice take away solution

To me, clean architecture is best explained by making the distinction between compile time dependencies vs runtime dependencies. It helps explain why interfaces and implementations are in separate layers

[smg]

Best tech video I've watched in a long time. Perfect level of detail.

[agustinustheoo]

Love this solution, can't wait to apply it myself!

[MaJoBeatIt]

Best architecture presentation I have watched and understood.

[michaelbui]

Not sure if I agree with data transfer object (dto) depending on Domain Objects (do). DTO are a communication concern not a data storage concern.

[xbitbybit]

Definitely needs to be more videos like this, you listening C# content creators? Show how things actually work in the real world, what the code looks like, so much better than just an explanation!

[dmsanz_youtube]

It's a very good talk on how to achieve clean architecture, but I disagree with the definition of domain and application layers. I guess the author is not following DDD, but domain is domain whether or not DDD is followed.

I don't think domain is the enterprise wide logic and types nor application layer contains business logic and types.

If we follow DDD, the domain layer actually has the business logic, it represents the business ubiquitous language. All the business rules are there. All the important domain validations, the model itself, etc. It's not enterprise wide, it is the bounded context wide.

The application layer has the orchestration of the use cases that delegate on domain layer to achieve state mutations. Command handlers for example.

But it's a good presentation!

[zensic]

Thank you! Lots of new topics to look into!

[abdulnaveed]

THIS IS A SAMPLE AMAZING, THANK YOU SO MUCH

[Miggleness]

The disadvantage of following clean architecture strictly are leaky abstractions and over abstraction. I personally prefer the simplicity of vertical slice architecture in JBogard's literature. Great talk on the topic. The template would be very helpful, too.

[christian.mar.garcia]

Very good talk, very informative. Thank you for providing the github repo.

[cutelittlebirdie]

This is so educational plus his voice is so asmr-y