Відео

Marilou Mission

Kiehn Villages

7546 Hessel Walks

We need more videos. the simplicity of your explanations is the glory

This is fantastic. Great explanation. I've seen this explained elsewhere in a book I think and for the life of me can't remember which but this is an excellent summary.

I was once in a project where I was forced to implement an architecture that is totally different to the team structure. it was a nightmare while the startup founder CTO lives in his ivory tower

I've been binge watching all your videos. Great stuff, I already knew some of this stuff but these are still really really clear and concise descriptions and you've had a thing or two to teach me too. This one's my favourite though. I'm mad keen on spoken language too and all your talk of tenses and moods and persons ticks two of my boxes at once. :)

Excellent! I've never really worked on any systems where Eventual Consistency is a thing... and I've, obviously, heard the term bandied about a lot... but never really known how it works.... until now! :)

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" :)

Beauuutiful explanations! Thanks a lot

awesome

Very Good

Great

Best explanation with short videos. I really like it. Understood well about DDD.. Please post a video related AWS migration from off-premises to ON premises for legacy application ex: Java application

great explanation! Thank you

Your Videos containing explanations in few minutes what workshops trying to say in hours. Thank you very much! Keep up! I will share it within my Team :)😊

Up! I appreciate videos like these because Agile has been abused by quickly trained Agile coaches with no real knowledge of IT. They are enforcing practices they don't understand, making teams miserable and ineffective, eventually making people completely turn away from Agile I'm not a fan of the whole commercialised thing, but it's clear that the core values make sense

Love your explanation thank you - I'm still on the fence about this paradigm. Again it feels like it was put together by some journeymen devs who were bored and felt they needed to invent something nobody asked for and probably another layer of bloat in microservice hell architecture. We developers often cite how complicated web development has become and its because of things like this.

Please take a look at spring modulith, it implements all the concepts you described in all your videos !

ua-cam.com/users/shortsBZxSDkVcwhU?si=HkQ2Ly-GnzI66pnE

For our new system I actually implemented an event-sourced system backed by SQL using efcore; it's typed, uses automatic JSON versioning and upgrade-on-read, as well as a strongly-consistent projections system where the projection state goes in the same transaction as the event append. Performance has actually been pretty great, and the way it makes rearranging the read model as requirements change has been absolutely amazing, I don't think I'd want to go back to a regular ORM.

Isn't Value Object a bit of an oxymoron, since objects usually have identity in OO? My brain wants to call them Value Types. They behave more like value types such as int and enum, and I also think they are easier to implement as structs rather than classes in C#.

I can't believe how clearly this video explains everything. It's the best comprehensive explanation I've had in a while.

Excellent video displayed in an animation, thanks a lot

Its most underrated channel. Thanks for good explanation. I request you one think please avoid music. Your explanation is very important cor viewers.

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 just earned a sub! Awesome explanation mate

Amazing video!! 👏

This is fine for atomic streams of operations that don't conflict received in order. Like 80% of website style transaction. However it does NOT scale horizontally. It provides, no, it refuses basic concurrency monitor controls and basics like "Test and set". Splitting a "Dequeue" operation into 2 concurrent/ordered operations leaves you wide open to race conditions, dead locks and I cannot see how this scales horizontally to accomodate increasing loads.

You deserve a lot more views and subscribers. Love how clear you explain things.

I have never faced the "hexagonal architecture" wording in my 11-years career

This is also somewhat i figured. Thanks for clarifying everything 👌

Great explanation, thank you!

an undervalued video with amazing explanation of so sophisticated topic. мое почтение

amazing video!

Thanks for your great content!

great video, thanks!

best

perfect♥

Well, not quite. Teams do not decide on cross domain integration and interactions. Architects do.

Ok, this has its cons. It is twice slower, because we need to do two additional DB operations which are slow. Second, don't deleta data from status table. Mark it as processed instead. This will keep tracking and reduce the possibility of double send.

what if you have huge data like 100000000comments in Post object. I don't think you can init a domain object with that much... looks useless to me when dealing with large chunks of data. Thoughts?

the ending is superb

exceptional well explained!

What toolset are you using to create these great videos? I supposed PowerPoint is one of them.

رائع .... حقيقي رائع !

I can't believe it. Best explanation ever.

This content for free? You are a blessing to humanity, mate. It has really removed many grey areas to my understanding of the topic. Thank you!

insane explanation thanks alot

At first glance I was thinking "Oh, drawing boxes is branching out from the technical videos of software engineering" The more I work in enterprise software development, the more I realize how important it is to also understand how you can work as knowledge worker in a team and how to communicate and plan even outside of it, so this video feels very much connected to the other content on this channel. Thank you!