Mainak Biswas.
Solution Architect, Author of Design Patterns - A domain agnostic approach
Nell Frédéric wrote:
For example if you take a classic SOA a good approach would be to migrate only the critical parts into MS. And even MS Architecture is an SOA Architecture (not a classical one, but it's one). You can have a classical SOA, a Domain Driver SOA or a MS SOA. But for me they are all SOA's... They just have different purpose and solve different problems. But MS Architecture could have been set up since REST was invented... It just it wasn't making any sense to have 100 Applications servers. It just became trendy because of the development of IaaS and PaaS solution.
But that's my point of view and I'm probably partially wrong.
“The strongest of all warriors are these two — Time and Patience.” ― Leo Tolstoy, War and Peace
Richard Rodger<br /><a href="http://www.ricebridge.com" target="_blank" rel="nofollow">http://www.ricebridge.com</a>
Richard Rodger<br /><a href="http://www.ricebridge.com" target="_blank" rel="nofollow">http://www.ricebridge.com</a>
That also brings up another question - does MicroServices and Containerization go hand-in-hand, or is it just that it is the preferred methodology to allow for many services, but without over-use of resources. I know we can run multiple servers on a single machine, but containerization is much easier.
So curious, in this new world, do you run Docker on your local machine, dev version of OpenShift, something else? Also what new tools are in your toolbox in the micro-services world?