This is so dope and simplified .. If only this video existed last year it would've made my life much easier. The company I work for is using a very similar architecture for their backend (Onion Architecture) and trust me it was such a pain in the ass understanding it especially as a junior backend dev.
Yes, great explanation, thank you! Would definitely check out the project implementation of this principle. Even though, the logic is pretty clear and understandable, when it comes to rl projects, it can get kinda confusing sometimes. Even just deciding on folder structure etc. :/
I agree with most of the ideas stated in the video. I use this architecture to teach new recruits in the company i'm in. I like how it separates the 3 main layers (Http/logic/DB) that often composes a modern backend. For new software engineers it is easier to understand when it is separated between files.The only tricky part for me is on where you declare your DTOS/Entities. You stated here that they are inside the business logic (which is fine by me) but when you use ORM, having Dtos that are not similar to the database model can cause some typing issue. I know it shouldn't be the case as your SQL model should be clean but on legacy application where the database cannot easily be altered, its always a headache. I have to admit that to solve this issue i've been guilty of using the types declared by the database model in the business logic (mostly because of laziness). Great video nonetheless for beginners that want to take it a bit further and start to design a more scalable project !
I've started working on a project using this architecture and the only drawback that I experienced was that because you are using dependency injection, it requires interfaces/types everywhere which prevents you from using type inference. Would love to see how you deal with this.
Thanks for a great video! You mention in the end you'd make a video where you'd explain these concepts while coding a Next.js application. Did you ever release that video? Would be really interested in watching it. If so, could you maybe link it?
Woukd love to see a backend project with same implementation
I was just looking up clean architecture for the first time, early this week. Thanks for making a video.
Very clear explanation! Thank you for clearing up some of my confusion
great work man, would be epic if you could build a full stack application with all these great practices
Been waiting for this. Thanks!
This is so dope and simplified .. If only this video existed last year it would've made my life much easier. The company I work for is using a very similar architecture for their backend (Onion Architecture) and trust me it was such a pain in the ass understanding it especially as a junior backend dev.
Love this type of content, would love to see a fresh t3 stack tutorial vid
Yes, great explanation, thank you! Would definitely check out the project implementation of this principle. Even though, the logic is pretty clear and understandable, when it comes to rl projects, it can get kinda confusing sometimes. Even just deciding on folder structure etc. :/
Just wanted to add regarding DTO. You make a good point at
This video is eye opening thank you !!
I agree with most of the ideas stated in the video. I use this architecture to teach new recruits in the company i'm in. I like how it separates the 3 main layers (Http/logic/DB) that often composes a modern backend. For new software engineers it is easier to understand when it is separated between files.The only tricky part for me is on where you declare your DTOS/Entities. You stated here that they are inside the business logic (which is fine by me) but when you use ORM, having Dtos that are not similar to the database model can cause some typing issue. I know it shouldn't be the case as your SQL model should be clean but on legacy application where the database cannot easily be altered, its always a headache. I have to admit that to solve this issue i've been guilty of using the types declared by the database model in the business logic (mostly because of laziness). Great video nonetheless for beginners that want to take it a bit further and start to design a more scalable project !
I've started working on a project using this architecture and the only drawback that I experienced was that because you are using dependency injection, it requires interfaces/types everywhere which prevents you from using type inference. Would love to see how you deal with this.
Thanks for a great video! You mention in the end you'd make a video where you'd explain these concepts while coding a Next.js application. Did you ever release that video? Would be really interested in watching it. If so, could you maybe link it?
Hey, with monorepo approach You can create lib with api-interfaces (if front-back are e.g. only TS). Great content
Good job babe!!!
some actual example of code structure would be awesome
Did you also create a Clean architecture Video for frontend?
11:00
I'm a bit confused, where should I put the transaction, commit, and rollback?
ForEach then Clean Architecture, nice ))