3 ms·
Sounds like a nightmare to me. Something that could've been a module in a regular application is split across multiple services introducing multiple network cal
by dsirola 7y ago
Sounds like a nightmare to me. Something that could've been a module in a regular application is split across multiple services introducing multiple network calls that can fail (not to mention the response time once the workflow grows).
If people who don't know how to write modular code start using microservices as a solution, the only thing that changes is that you end up with distributed big ball of mud instead of the regular big ball of mud.
- redact207 7y agoIt's worth clarifying that workflows are generally used to coordinate long running processes that can last up to days - think coordinating receiving an order, picking, dispatch etc. It's not intended to fit within the space of an http request/response. As for should everything be in a module? Idk, but it's a much nicer place to start than microservices
- romanovcode 7y agoCongratulations, you've just described 90% of microservices.
- jbverschoor 7y agohttps://mathservice.my.org/api/v1/multiply https://mathservice.my.org/api/v1/multiply