3 ms·
Related: a detailed 50-minute talk about using Consul at scale (for service-discovery) at DataDog, by Darron Froese. (The talk was given at SREcon16, on 04/08/1
by qohen 10y ago
Related: a detailed 50-minute talk about using Consul at scale (for service-discovery) at DataDog, by Darron Froese. (The talk was given at SREcon16, on 04/08/16.)
We had many VMs in AWS - were ingesting millions of metrics per second - and were having pain around service discovery and quick configuration changes. This is the story of how we integrated Consul into our environment, what it helped us with, mistakes we made and some tips for successful implementation in your own environment. 10 months later, our growing cluster was using Consul to facilitate 60 second cluster-wide configuration changes and make service discovery simpler and more flexible.
Video (and audio):
https://www.usenix.org/conference/srecon16/program/presentation/froese https://www.usenix.org/conference/srecon16/program/presentat...
Slides and code:
https://blog.froese.org/2016/04/08/srecon-running-consul-at-scale/ https://blog.froese.org/2016/04/08/srecon-running-consul-at-...
- josegonzalez 10y agoThis was a great talk. I shared it with our other ops engineers at SeatGeek and it mirrored our experience exactly. Hell, we even ended up with similar projects for writing out shared config files to consul to get around early consul perfect issues.