orchestration

I am evaluating Kubernetes (with Docker containers, not Kubernetes) and Docker Swarm and could use your input. If I'm looking at 3 (8.76 hours) or 4 (52 min) 9's reliability in a server farm that is < 100 servers, would Kubernetes be overkill due to its complexity? Would Docker Swarm suffice? Docker swarm will be able to meet your requirements. I recommend you start with Docker swarm as it is robust and very straightforward to use for anyone who has used Docker before. For a Docker user, there are many new concepts that you need to learn to be able to use Kubernetes. Moreover, setting up

Is an Enterprise Service Bus (a tool that acts as a mediator, a message broker, a service enabler, schema transformation enhancer, transparent location provider, service aggregator, load balancer, monitor, and all that stuff) responsible to orchestrate services ? What about putting an automated business business process with more than thousand steps and dozens of service invocations inside your enterprise service bus? Would you do it, or would you use a specialist in orchestration such as a BPEL engine? Please gimme you opinion. Yes and no. There's a thin, and sometimes indistinguishable line

I'm an architect in a large scale financial company and we are in the beginning of implementing a new business oriented infosystem across our different countries. From the very early on the core idea has been to follow microservice oriented principles as much as possible (and making sure engineers have read Building Microservices book by Sam Newman) . By now I've come to crossroads. Our services are primarily JSON REST services using Swagger for automated documentation, but in order to use these services in our business processes and making sure not to write business logic into services