Skip to main content
Case Study

Jet.com - Nomad Auto-Proxy with Consul-Template and NGINX

Justen Walker explains how Jet.com uses HashiCorp Consul and Nomad to allow hundreds of developers to have self-service access, despite relying on NGINX static configs—and with a remarkably small DevOps team.

In production, Jet.com has 40+ Nomad agents, controlling 300+ jobs, composed of hundreds of microservices.

Justen's DevOps team also uses the NGINX load-balancer to route all its HTTP traffic. But the team is small—fewer than 20 people to service hundreds of developers—so to prevent becoming a bottleneck, they needed a way for developers to self-service. And that's a problem, because NGINX requires static configs.

In this talk from HashiDays NYC 2017, Justen covers: * how they set up Nomad and Consul to achieve this * how they prevent "brittle" NGINX configs from becoming a problem * how they implement multi-region support * gotchas, tips and tricks

Speaker

More resources like this one

2/1/2023Case Study

Should My Team Really Need to Know Terraform?

7/21/2022Case Study

Using Terraform Enterprise to support 3000 users at Booking.com

2/22/2020Case Study

Terraforming RDS: What Instacart Learned Managing Over 50 AWS RDS PostgreSQL Instances with Terraform

10/7/2019Case Study

Running Windows Microservices on Nomad at Jet.com