3 ms·
After reading this thread I had to read this [1], which I found helpful in understanding the discussion. I think in some cases it is just more natural to write
by dwringer 9y ago
After reading this thread I had to read this [1], which I found helpful in understanding the discussion. I think in some cases it is just more natural to write microservices but at the end of the day if done right the end user won't really know the difference, it's all just SOA(?)
[1] https://stackoverflow.com/questions/25501098/difference-between-microservices-architecture-and-soa https://stackoverflow.com/questions/25501098/difference-betw...
- dboreham 9y agoParticularly the comment on that SO question that begins "There is no difference..." So many names for the same thing (that hardly anyone can agree on what exactly it is). No wonder the doctors and lawyers and accountants take all the money.
- jdmichal 9y agoHere's some things off the top of my head: * Single business function. Microservices don't have to be small, but all their calls should facilitate s single business function. * Automated deployment. Services are deployed and undeployed live based on load. * Unknown targets. Services are allocated and deployed to machines at runtime. The machine itself may even be allocated on demand. So service discovery is absolutely required. * Stateless. Services instances can be spun down at any moment, so they can't be holding transaction state.