Clean Architecture in .Net
Stephan Hoekstra

Another question: why do you use one particular class for one use case? Looks as if you used the Command-pattern. Is that part of clean architecture or is it just your idea? Will cause in many classes in a big application…

As an option, I can imagine to simplyfy it by useing _one_ class (as a layer) with many methods — each method for one use case. Would that be clean, too / conform to clean architecture?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.