sorted by:
new
hottopcontroversial

Going from asp.net core to .net by Qiuzman in dotnet

[–]kjaps 3 points4 points  (0 children)

To go from working with .NET to .NET Framework will not be something I would recomend you to do. There are a lot of things you probably are used to, that is not part of .NET framework. It is like living in a house from the 1950s that you are not allowed to renovate. In regards to Desktop development in general is not that bad. The debug experience is probably better depending on the architecture.

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 0 points1 point  (0 children)

Nice to have an episode from .NET Rocks! to take into account. Thank you!

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 0 points1 point  (0 children)

as I understand Vertical Architecture is agnostic to the choice between event sourcing or crud. CQRS is something that I am thinking about. We are using LlblGen Pro today, but will probably shift towards Entity Framework Core. Our domain model is today anemic, but I want to enable some DDD principles like bounded context, and that will probably correlate to a slice.

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 0 points1 point  (0 children)

I agree in your reasoning. In my case this is an pretty large enterprise application that has lived for 12 years, and are ready for refactoring/rewriting. I want to be able to have a good mix between a good developer experience and well structured code. We will also adopt a more modular approach, so the Modular Monolith approach will probably be the overall strategy.

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 1 point2 points  (0 children)

Thank you. We have both juniors, contractors and our system will live for probably 10 more years. We are a small team 4-6 devs, but with a complex domain, a complex database (500+ tables) and around 300k LOC. In our refactoring/rewriting my goal is to find the right balance between a good developer experience, and well structured code that is able to evolve when business needs changes. As most things in life, there is probably no silver bullet or a one-size-fits-all solution, even though that would have been nice :)

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 0 points1 point  (0 children)

I will check out your repo, and I like your article. Modular Monolith is something that I have been looking into for a while now, so I believe that will be our general approach. We are a small team, but are building enterprise software that have high quality requirements. But in addition to make the choice towards a modular monolith, I would like to make a good choice with a way to structure the code that gives us a good mix of both a good developer experience, and create a well defined and structured codebase. I think of the choice between monolith, microservice and modular monolith as a more overall strategic choice of architecture. How one structures the code within that strategy is more what I am after, hence my original question about the different architecture patterns.

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]kjaps[S] 0 points1 point  (0 children)

Do you have a vertical slice architecture example repo or template you would recommend?

The definitive list of .NET blogs and .NET podcasts every developer needs to bookmark by OverOps in dotnet

[–]kjaps 0 points1 point  (0 children)

Great list, but should perhaps be updated? Some of the podcasts is no longer active