3 ms·
I am always amazed about the Hasicorp tools. What I really like that they solve problems I did not think about (yet). What I think is their biggest advantage is
by weitzj 11y ago
I am always amazed about the Hasicorp tools. What I really like that they solve problems I did not think about (yet).
What I think is their biggest advantage is their ability to integrate in a heterogenous infrastructure - you do not need to throw away your current infrastructure setup. You can gradually integrate tools like Consul/Consul-template. You do not have to install for example Docker.
And I guess otto is a nice tool which solves the problem to deploy AND develop a microservice architecture. So maybe you already got your part right, where developers push a new microservice to production, and the production setup runs fine. There might still be problems how a developer can create a local development environment with multiple microservice depedencies, which you might want to have locally. The best solution in my opinion is fig.sh(docker-compose) right now. But docker-compose does not help you for deployment (and you have to depend on Docker)
- krakensden 11y agoReally? I feel like half of my time working with hashicorp tools is spent cursing. Vagrant takes more time to parse its ruby code than it takes to boot a vm and its guest. It breaks my coworkers routing on a regular basis. Terraform breaks for almost everything I've tried it with- no, deleting my infrastructure and rebuilding it from scratch is not acceptable in production. Consul is a distributed dowtime protocol, using a modern, peer reviewed consensus algorithm, and a gossip protocol for auto-partitioning of your network.
- weitzj 11y agoI just use consul/consul-template and Vagrant (+ Puppet) right now. Vagrant works just fine, I do not experience routing problems. But I will remember your advice/experience for our future plans.