While building it yourself is certainly a good way to learn; building a project that you want is best. You learn along the way.

However, in this case, the best way to learn about such a prolific topic is to stop reading sources that fawn about these things and start to learn about the flaws and criticisms.

Great thinkers like Uncle Bob, have brought many useful ideas to software development, but they are not infallible. You find out where they are wrong, but reading from reputable skeptics.

Here are some good skeptical sources

• @Robert Bräutigam's comment
• What is overengineering applied to software - https://stackoverflow.com/a/1001499/887092
• Video: Object-Oriented Programming is Bad - https://www.youtube.com/watch?v=QM1iUe6IofM
• Skepticism of Uncle Bob's clean architecture - https://dev.to/bosepchuk/why-i-cant-recommend-clean-architecture-by-robert-c-martin-ofd
• Is ORM an anti-pattern - https://softwareengineering.stackexchange.com/a/120338/78712. Your propensity to using Dapper instead of the "heavy" EF is telling.

Now, you don't need to agree with all skepticism, but it's important that you are exposed to them, so you can make informed decisions in your professional software programming career.

My company is working on a draft new open standard for cutting through the hype of "software architecture". The best relevant starting point, is the comparison to microservices - https://colossal.gitbook.io/microprocess/comparisons/compared-to-microservices

It's possible to contain complexity within the data-layer entirely and fully decouple mutating processes, and thereby reduce the amount of host infrastructure, eliminate custom middleware code (where security bugs arise), and reduce technical debt.

While building it yourself is certainly a good way to learn; building a project that you want is best - you will learn along the way.

However, in this case, the best way to learn about such a prolific topic is to stop reading sources that fawn about these things and start to learn about the flaws and criticisms.

Great thinkers like Uncle Bob, have brought many useful ideas to software development, but they are not infallible. You can find out where they are wrong, by reading from reputable skeptics.

Here are some good skeptical sources

• @Robert Bräutigam's comment
• What is overengineering applied to software - https://stackoverflow.com/a/1001499/887092
• Video: Object-Oriented Programming is Bad - https://www.youtube.com/watch?v=QM1iUe6IofM
• Skepticism of Uncle Bob's clean architecture - https://dev.to/bosepchuk/why-i-cant-recommend-clean-architecture-by-robert-c-martin-ofd
• Is ORM an anti-pattern - https://softwareengineering.stackexchange.com/a/120338/78712. Your propensity to using Dapper instead of the "heavy" EF is telling.

You don't need to agree with all skepticism, but it's important that you are exposed to them, so you can make informed decisions in your professional software programming career.

My company is working on a draft new open standard for cutting through the hype of "software architecture". The best relevant starting point, is the comparison to microservices - https://colossal.gitbook.io/microprocess/comparisons/compared-to-microservices

It's possible to contain complexity within the data-layer entirely and fully decouple mutating processes, and thereby reduce the amount of host infrastructure, eliminate custom middleware code (where security bugs arise), and reduce technical debt.