|
|
|
|
|
|
by gopher_space
404 days ago
|
|
|
Microservices 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. |
|
|