I really like your videos, they explain everything clearly, though I have a little bit of a different opinion here regarding monolith. Yes it is frequently become a "spaghetti jungle" what I'v seen in many companies I worked for, but I think there are use cases where the monolith application is the preferable choice considering the expected scalability, deployment and cost. The business scenario and so on. It this case a monolith application should be built in a clear and modular way following best practices, separation of concerns, business logic, therefore it will be easy to maintain, and the code in a properly structured monolith can be easy to follow, modify. If it is done in a proper modular way, there is a way to split it up later in that unlikely scenario that it has to be ported to a micro-service architecture. I am saying "unlikely" because before making the decision of the right architecture I assume it was assessed properly which solution fits the business case.
You're welcome! The chapter from 0:52 in this video briefly touches on the modular monolith. It basically isolates subsystems to get logical separation and the ability to develop and test them independently (like microservices), but the subsystems are still hosted in one process and deployed as one unit. Maybe I'll do a more focused video on that soon
Hope you will create more content on DDD and Micro services. It's very helpful
Cool... "Brian Foote and Joseph Yoder"... it's great to have a name (or, two names, in this case) to attach to the term "big ball of mud" :)
Please, keep posting these amazing videos! :D
these videos make complex topics easy to understand in around 5 min.💯. Thank you and as others have said please make more 😉
Brilliant videos!
How i wish we could have an architect like you on our team ;)
Love your videos!
What a masterpiece of work!🎉
I really like your videos, they explain everything clearly, though I have a little bit of a different opinion here regarding monolith. Yes it is frequently become a "spaghetti jungle" what I'v seen in many companies I worked for, but I think there are use cases where the monolith application is the preferable choice considering the expected scalability, deployment and cost. The business scenario and so on. It this case a monolith application should be built in a clear and modular way following best practices, separation of concerns, business logic, therefore it will be easy to maintain, and the code in a properly structured monolith can be easy to follow, modify. If it is done in a proper modular way, there is a way to split it up later in that unlikely scenario that it has to be ported to a micro-service architecture. I am saying "unlikely" because before making the decision of the right architecture I assume it was assessed properly which solution fits the business case.
Yup, spot on! There are always trade-offs to consider. Sometimes a modular monolith is exactly the way to go
Great video!!!!!!!!!!!
great video, thanks!
good content!
Hi thanks for great content
can you please make a video about modular monolith vs microservices?
You're welcome! The chapter from 0:52 in this video briefly touches on the modular monolith. It basically isolates subsystems to get logical separation and the ability to develop and test them independently (like microservices), but the subsystems are still hosted in one process and deployed as one unit. Maybe I'll do a more focused video on that soon
Gread vid!
Thanks! Glad you're enjoying these videos
❤🔥