The three tools that we have looked are not the only schedulers available, there are also tools such as the following to name a few:

All these schedulers have their own requirements, complexities, and use cases.

If you had asked me a year ago which of the three schedulers that we have looked in this chapter would I recommend, I would have said Amazons EC2 Container Service. Kubernetes would have been second and I probably wouldn't have mentioned Rancher.

In the past 12 months, Kubernetes has vastly reduced its complexity when it comes to installing the service has removed its biggest barrier to people adopting it, and as we have demonstrated, Rancher reduces this complexity even further.

Unfortunately, this has left EC2 Container Service feeling like it is a lot more complex to both configure and operate when compared to the other tools, especially as both Kubernetes and Rancher support launching hosts in Amazon Web Services and can take advantage of the myriad of supporting services offer by Amazon's public cloud.

In our next and final chapter, we are going to be reviewing all the tools that we have looked at throughout the previous chapters, we will come up with some use cases as well, and talk about the security considerations that we will need to take when using them.