> Bleah. I hate articles like this. They regurgitate all the well known talking points about enterprise software development but none of the realities of micro services.
I disagree. The post is a good summary of all the key features and main concepts of a microservices architecture developed with domain-driven design. It does what it says on the tin, and you don't have to read three books to get there.
> It sounds like they haven’t actually worked in the trenches supporting and coding real microservices at scale.
I have no idea where you got that idea. It certainly wasn't from the blog post, though.
> The realities are that going from monolith to microservices is a huge investment, and only large engineering teams should do this migration.
Your rant makes no sense at all. You're just mindlessly repeating cliches about issues that have absolutely nothing to do with the subject. I mean, the blog post is about microservices software architecture with domain-driven design and clean code, but here you are whining about how you believe refactoring projects designed following an entirely different architectural style is hard.
My point is everything they talk about is common to any type of enterprise software development. It’s not new. And then they slap on “microservices” at the end so they can claim to have written something new.
If they want to write something new then talk about the realities of how microservice development is different than regular enterprise software development. Not regurgitating the same old concepts and pretending it’s eye opening and new.
Um, it may not be new to you but it is new and eye opening to me and there might be hundreds or thousands of people who haven't read about this. From a newbie's POV, I quite like how the author explains the concepts with the example of an e-commerce company. Sure there will be advanced concepts but the author makes no claims that he is addressing that audience :) .
> My point is everything they talk about is common to any type of enterprise software development. It’s not new. And then they slap on “microservices” at the end so they can claim to have written something new.
Again, your rant makes no sense at all. The blog post talks about a specific distributed system architecture style whose services are designed following a specific architecture style.
And here you are, angry at someone because... Because you believe the author has ulterior motivations?
> If they want to write something new then talk about
Sorry, but you have no authority to tell others what they should or should not write.
The author of this post contributed something to the public that's interesting and has value. Meanwhile what have you done?
It’s inherent in this comment that you really don’t understand DDD and why adhering to its precepts is a critical improvement in designing microservices.
Plenty of books to read, videos to watch. Learn/listen before you speak.
I disagree. The post is a good summary of all the key features and main concepts of a microservices architecture developed with domain-driven design. It does what it says on the tin, and you don't have to read three books to get there.
> It sounds like they haven’t actually worked in the trenches supporting and coding real microservices at scale.
I have no idea where you got that idea. It certainly wasn't from the blog post, though.
> The realities are that going from monolith to microservices is a huge investment, and only large engineering teams should do this migration.
Your rant makes no sense at all. You're just mindlessly repeating cliches about issues that have absolutely nothing to do with the subject. I mean, the blog post is about microservices software architecture with domain-driven design and clean code, but here you are whining about how you believe refactoring projects designed following an entirely different architectural style is hard.