9 ms·

Is it the word micro that causes the issue? Services are way easier and more logical when they are verticals - this is how it's largely meant to be. How many pe

Is it the word micro that causes the issue? Services are way easier and more logical when they are verticals - this is how it's largely meant to be. How many people have read the supporting books and literature that say as much? That would be a good question. Almost everywhere you go, you see the same mistakes. Almost every one can be found in Sam Newman's 2nd edition. The conclusion I draw is that a very large number of developers ran with it without understanding the pros and cons. Services are only worth it if your organization benefits more from the pros. Many orgs don't, so it makes no sense for them to adopt it over monolithic architecture that is way easier to implement transactions with. Designing "transactions" across services and databases is an insane endeavour. It's best if each service is split on a line that it can deal with incomplete states in other services.

marcosdumay 3y ago
The "micro" was specifically coined to mean breaking a vertical into several smaller services. So, if you go look online how to create microservices, you will get most of the material biased into that. Even though most people pushing those describe something saner, what the docs say is what you will get. Before that, we had "SOA", that was coined to mean exactly breaking your system into full verticals. But then the term was hijacked by some very loud companies selling tools for microservices, and now if you go search for it you will mostly find stuff like how to set distributed transactions. Overall, humanity currently has a pretty hard time communicating, due to the sheer number and size of bad actors actively and purposefully polluting our communication infrastructure. We get to feel the effects when talking about software too.
donkeyd 3y ago
> Is it the word micro that causes the issue? Services are way easier and more logical when they are verticals I think that the word micro is indeed the issue. Once they stop being micro and just become services, it pretty much becomes a Service Oriented Architecture. So why keep calling it microservices?

marcosdumay 3y ago

The "micro" was specifically coined to mean breaking a vertical into several smaller services. So, if you go look online how to create microservices, you will get most of the material biased into that. Even though most people pushing those describe something saner, what the docs say is what you will get. Before that, we had "SOA", that was coined to mean exactly breaking your system into full verticals. But then the term was hijacked by some very loud companies selling tools for microservices, and now if you go search for it you will mostly find stuff like how to set distributed transactions. Overall, humanity currently has a pretty hard time communicating, due to the sheer number and size of bad actors actively and purposefully polluting our communication infrastructure. We get to feel the effects when talking about software too.

donkeyd 3y ago

> Is it the word micro that causes the issue? Services are way easier and more logical when they are verticals I think that the word micro is indeed the issue. Once they stop being micro and just become services, it pretty much becomes a Service Oriented Architecture. So why keep calling it microservices?