Good to see you back man ❤

Thanks, one of the most clear templates on internet!

great to see you making another video!😊

FYI, I don’t need a reminder to tell you I love you 🤣

Good content. Thanks! Definitely some nuggets of information that I can use in my Clean Architecture journey.

I actually love how the Authentication is done Here. I have a quite similar Solution Template where much more things are Automated, especially the repository with caching, but authentication is a Part i am missing currently.

Thanks for sharing. This is great!

That's great video Amichai 🙂

so many clean architecture templates out there, i will take a look

Welcome back!!

Cool template, mine's pretty close, but I learned some new stuff to add to mine from yours! Thank you

Hello Ami, it's great to have you back man. Just to be sure and for the sake of other viewers who will be watching this, the step involving the conversion of incoming requests into commands or queries does not necessarily imply the usage of the CQRS architectural pattern. Does it?

Thank you!

You are the best!

Thanks Amichai, wish to make a playlist for real-time in .Net

nice video, I have a question, if I have some azure durable functions with service bus triggers that handle business processes, where would you locate them?

Nice one Amichai. I review such templates. Heads up: I noticed the short name clashes with Steve "Ardalis" Smith's template (clean-arch), so they don't work on the same machine in parallel unless you specify the full name. I'm especially interested in how you handle repository querying/specifications; Ardalis' Specifications library being on my lookout. I'll give a proper review after trying this out in use cases

Thanks, What do you think about using the domain models directly as the database entities or creating a persistence model for the database and then mapping them back and forth between domain to db entity and vice versa? I saw it as a challenge in real-world apps when having a complicated domain entity to be used directly as a database entity, at the same time, the mapping between domain models/persistence models also a challenge sometimes

Great template! Very close to Jason Taylor's with a few tweaks. One thing I'm surprised about the sample code is the Amichai allows Entities to be created in an invalid state. I can create a Reminder with a NULL text field, or a user with NULL first, last, and email. Obviously not an issue with the template, just an observation of the sample code.

too sad that such monolithic architectures era is ending. I wonder how we can apply this to a microservice approach.

Thanks for both the video and source code! 🙌 Do you happen to have any other videos / good resources more specifically on the policy implementation and how policies can be structured for scalability, simplicity and maintainability?

אחלה ווידאו :) , אני ממליץ לך להשתמש ב minimal api, זה נכנס חזק עכשיו

Nice video. Thanks. May I ask, how do you make these explanations, arrows and boxes in live video?

Great video 🎉 you are using wich tool to draw arrow and box on your screen ?

In your clean architecture tutorial playlist you used Aggregator pattern. Here you dont have that. any specific reason for that ?

Very cool and organized structure 👍, I will check it in my next projects. Could you please tell me what this tool that you used to highlight and write on screen, I like it.

Hey Amichai, I am having a lot of trouble trying to deploy this demo on K8s. Can you give a couple of tips? I am just trying to create an image based on your docker file but it is not working. I want to show my boss that this should be how to work properly. But still, no luck deploying

Great content🙂! I'm curious, will there be a sequel to your DDD and Clean Architecture courses on DomeTrain? It feels like some key pieces are still missing, particularly on the unhappy path 1) Eventual consistency within the domain while processing the domain events goes wrong(just sending an email is not realistic, what if we need to roll back) 2.Integration events handling and transactions between microservices(MassTransit with Outbox and Saga patterns?)

Help. My authorization not working. Did anyone has same issue ?I implementing IAuthorizable on one of the request and added Authorize attribute. I did register openbehaviour Authorization. What am I missing. IAuthorizable should be added somewhere ?

would love a simple blazor frontend

May I know how the AppDbContext works in Repository without constructor?

We came up with an almost identical project arrangement in a new solution recently. I remember a lot of discussion around having separate Domain and Application project layers. We ended up having a single project for domain and application because it didn’t seem like having two added much value. Obviously every project has different needs, but when do you think it makes sense to truly separate the Domain from Application?

Great courses in dometrain 🔥

Can you provide a quick comment on why you are seperating the API requests and responses in an other class lib.? It looks neat but is it the only reason?

Just one question, I saw that the permission goes in the claims, when the project scales this could be a problem because it could end up with too many permissions, slowing down all requests because the token is very large. Will it be possible to change it so that it is validated in the persistense or identity, based on a userid from the claims?

I noticed that the logic of the commands is in the domain class User (e.g., DismissReminder). I'm a little confused now, isn't the application's layer job to handle the logic? Why do we have that in the domain layer instead?

Does anyone know how Amichai draws those arrows/ boxes? Is that a program or smth?

How do you Return a qualified not authenticated http response for your Controllers when using mediatr middleware to check

Where would you locate hubs from signalr?

Why do you place your repository interfaces in Application instead of Domain layer?

Clean Architecture was nice in its time when we were working on larger monolithic OOP applications. Not so much value today.

I wonder why most authors expose foreign keys in entities when representing relationships. For example: Why not private readonly List _reminders = []; Instead of private readonly List _reminderIds = [];

Mwahh prefer DDD, this seems so hackish

Having infrastructure is debatable. I love to have each domain completely independent from each other. Having contracts only to interact with it. Inside domain in a namespace is infrastructure code. Likewise each domain does not rely on common table or infra. Goes into this modular monolith. Even endpoints could be out of API in a separate project to leave api just a dumb shell and bootstrap

I think sometimes that .Api and .Application levels must be named in some other manner. Because i had some cases when it was useful to code several applications sharing the same domain. For example, CRUD service (working with database as signgle replica), some business service (working with message brokers as several replicas) and may be can exist some desktop application like WPF- or Avalonia- based application. The exact structure of services can be re-organized after changing of actual production workload, but it`s definetely cannot be the reason to change domain - just re-structure applications that use this domain. So i think that top level project can be named not only as .Api, but also as .App. It would be very convenient. But in this case, it would be similarity between .App and .Application. So the idea is not completely good. I would hear some sample of such cases, because i think that Clean Arch is mos powerful exactly in sutuations with multiple Api or applications with shared domain, in this case some architecture levels becomes more justified.

Hello sir, I was a member on patreon but due to some financial issue it will not be possible to continue membership and a also want to study Deep Dive: Clean Architecture in .NET course but i'm not able to pay you as course fee $89.99 could you provide me low fee for that course.

"ultimate"? 😶