3 ms·
I’m honestly not trying to be snarky here but I didn’t know there was any other way to design microservices (with intention) that weren’t domain oriented.
by etxm 6y ago
I’m honestly not trying to be snarky here but I didn’t know there was any other way to design microservices (with intention) that weren’t domain oriented.
- timclark 6y agoI’ve seen one service per database table, and have had architects seriously think that a table equals a bounded context. Then they try to work out how to do two-phase commit across micro services.
- etxm 6y agoOh that. I’ve had to merge services like that. People are always grabbing nouns and thinking they’re microservices.
- fma 6y agoI'm on the same boat. "Previously product teams would have to call numerous downstream services to leverage a domain; they now have to call just one....Furthermore, we were able to classify 2200 microservices into 70 domains." So they went from 2200 to 70 microservices? One extreme to the other. The answer is somewhere in the middle.