25 ms·
I'm not speaking from experience here, but it seems like rather than "moving to a microservices architecture" it would perhaps be better to think more in terms
by contextfree 5y ago
I'm not speaking from experience here, but it seems like rather than "moving to a microservices architecture" it would perhaps be better to think more in terms of "splitting out specific functionality X into an independently deployable and hostable service, which should alleviate the specific problem Y that we've been experiencing due to their being too closely coupled" and if there are no obvious X and Y then maybe the "monolith" is fine?
- wpietri 5y agoFor sure. Find a problem first, then look at solutions. Try one out, see if it helps. If not, try a different solution. Man-with-a-hammer syndrome is dangerous.