Friday, March 25, 2016

7 reasons why you should be using CoreOS with Docker

Finally, here are the top reasons to try out CoreOS: Reason #1 to go with CoreOS is etcd which was mentioned above. As the CoreOS website says: "Configuration values are distributed within the cluster for your applications to read. Values can be changed programatically and smart applications can reconfigure automatically. You'll never have to run Chef on every machine in order to change a single config value ever again." Reason #2 If you care about high availability at all, deploying using CoreOS is one of the best ways to achieve that with a relatively low price point. Reason #3 It lets you serve different versions of software on different machines and update machines without any downtime Reason #4 Though Docker helps you provide similar environments in production and development, CoreOS goes one step further by replicating cluster and network settings between dev and prod as well. As discussed before it also makes sure that the infrastructure always has the right configuration and everything has the right versioning. Reason #5 New developers can get up and running quickly rather than waste time installing all the required software and versions on their machine and making sure that nothing conflicts. Reason #6 It can drastically reduce cost by replicating software services like Heroku. Even though you need multiple machines to truly take advantage of CoreOS, CoreOS is now supported by every major cloud storage provider, including AWS and Digital Ocean, the latter of which provides machines for only $5/month. Reason #7 It has a very active open source community with (at the time of this writing) 6764 stars, 172 contributors, and over 40 pull requests merged in within the last two weeks for etcd. This may potentially be a problem, as one of the central tenets of the security that CoreOS offers out of the box is automatic updates on all your machines. Though you cannot turn this feature off, you can select an update strategy to control when and how your machines will update.

No comments:

Post a Comment