Looking for books & other references mentioned in this video? Check out the video description for all the links! Want early access to videos & exclusive perks? Join our channel membership today: th-cam.com/channels/s_tLP3AiwYKwdUHpltJPuA.htmljoin Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
As a platform engineer trying to get us out of the coupled module situation this hits the nail on the head. the defining quality is independently deployable. let's consider and leverage the guarantees and qualities present in our services.
In other words, the architecture dictates the versioning and repository patterns as well. Architecture is best when it is allowed to evolve. Shouldn't versioning and repository patterns also be allowed to evolve and change when needed?
@@dvanrooyen1434 do you get to test every particular version of a browser with every particular version of a http server? Or do you expect them to implement http properly and test for that?
I will not agree with your conclusions, yes you can make monorepo work but isn’t not free either. So you advocate as a benefit your ability to go and change someone else module without coordination with the responsible team, yes it may save your some time to implement changes you! care about I totally get it. But what about other team? Are you 100% sure that you understand their intentions behind codebase you just changed? If this code will brake in some unexpected way who should take responsibility for the break? My experience shows that most of monorepo end up as big ball of mud just because it’s too easy to change someone else code to save the effort. Is it possible to keep monorepo clean? Sure it is but it requires constant vigilance is it very difficult to achieve. In my practice I use different repositories specifically where I want to make changes difficult to keep entropy under control.
Looking for books & other references mentioned in this video?
Check out the video description for all the links!
Want early access to videos & exclusive perks?
Join our channel membership today: th-cam.com/channels/s_tLP3AiwYKwdUHpltJPuA.htmljoin
Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇
As a platform engineer trying to get us out of the coupled module situation this hits the nail on the head. the defining quality is independently deployable. let's consider and leverage the guarantees and qualities present in our services.
"The worst of both worlds"
Somehow, SW developers have a knack for getting themselves in this position. Same with the adoption of "Agile" development.
The topic that just won't die 😂
well, people keep doing microservices no matter what
Folks have to put bread on table…never ending story indeed
In other words, the architecture dictates the versioning and repository patterns as well. Architecture is best when it is allowed to evolve. Shouldn't versioning and repository patterns also be allowed to evolve and change when needed?
You don’t get to test the interaction of these services before release??? Ahh man I was looking forward to this and will end it right here…
@@dvanrooyen1434 do you get to test every particular version of a browser with every particular version of a http server? Or do you expect them to implement http properly and test for that?
Good stuff, mixed with a bunch of crock.
Why are you saying Monolith when you mean monorepo? Monolith is an undevisable single service. Monorepo can contain many micorservices inside.
I will not agree with your conclusions, yes you can make monorepo work but isn’t not free either.
So you advocate as a benefit your ability to go and change someone else module without coordination with the responsible team, yes it may save your some time to implement changes you! care about I totally get it. But what about other team? Are you 100% sure that you understand their intentions behind codebase you just changed? If this code will brake in some unexpected way who should take responsibility for the break? My experience shows that most of monorepo end up as big ball of mud just because it’s too easy to change someone else code to save the effort. Is it possible to keep monorepo clean? Sure it is but it requires constant vigilance is it very difficult to achieve. In my practice I use different repositories specifically where I want to make changes difficult to keep entropy under control.