3 ms·
1. How does this really differ from debugging both services at the same time and attaching logpoints? 2. Microservices is a team separation technique, allowing
by randomdata 3y ago
1. How does this really differ from debugging both services at the same time and attaching logpoints?
2. Microservices is a team separation technique, allowing different team to live in isolation, sharing only API documentation. It's the same as regular web services, except within a single organization instead of across organizations. If you happen to have access to the code (not a guarantee!), are you really going to be able to jump into a codebase you're not familiar with to start adding print lines with more expediency than other possible approaches?
- rolisz 3y agoRe 2: tell that to the company I used to work with. Management heard microservices are good? Then we should have nano services. They mandated that we split things up super small, by functionality, even if there was only one team working on that.
- edgyquant 3y agoMicroservices are more than just an organizational abstraction. They allow you to scale up services as needed for one thing.
- randomdata 3y agoYes, that's right. Teams not needing to communicate, beyond API contracts, allows them to scale the service they provide. When sharing code in a monolith then you have to meetings when you want to make changes that impact other developers, and that will soon take your whole day when there are thousands of workers, leaving no time to do anything. That leaves service that cannot scale. More simply, it takes how the macro economy scales software (and, really, most everything) and tries to apply the same processes in the micro.
- sanderjd 3y agoA service layer is not necessary to have an API contract.
- randomdata 3y agoBut you do need people providing service in order to emulate macro services in the micro.
- sanderjd 3y agoI honestly can't make heads or tails of this. Can you expand on what you mean?