3 ms·
There are plenty of tech reasons for microservices. e.g. scaling high traffic services separately and separating low priority functionality from critical paths
by fallingknife 1y ago
There are plenty of tech reasons for microservices. e.g. scaling high traffic services separately and separating low priority functionality from critical paths. I would agree that this is usually not a smart thing to do in a small org, but I have seen times where splitting out a high load path into a microservice has been very much worth it at a startup.
- bluefirebrand 1y ago> scaling high traffic services separately This is a great optimization once you have high traffic services Building this way before you have any traffic at all is a great way to build the wrong abstractions because your assumptions about where your load will be might be wrong
- gopher_space 1y agoMicroservices are a technical solution to regional availability and pairing problems, and they start with a spreadsheet telling you when to make them based on requirements vs. cost. They're slow, expensive threads you should have a really good reason to use. > Building this way before you have any traffic at all is a great way to build the wrong abstractions These services only make sense to think about within specific traffic contexts. It'd be impossible to build the right abstraction.