Tinder Engineering recently updated our blog with a post about some exceptional technical work by the Cloud Infrastructure Team.
At Tinder, we run hundreds of microservices that all have unique network configurations, roles, metric rollups, and environmental variables (“env vars”). This myriad of configurations within the cloud makes it difficult for developers to know if the code they write will actually work once deployed.
We needed a general-purpose solution that leveraged the same (or very similar) configuration as prod, and was accessible early in the development cycle.
To solve the above problems, we decided to go with a software-based solution called Ignis. Ignis is a CLI tool written in Golang that empowers our developers to run only the service they’re developing locally and forward/receive their traffic to/from a shared development Kubernetes cluster.
tl;dr Ignis makes it feel like you have the entire Tinder platform - 500+ microservices, AWS, and all - running locally on your laptop. This was a productivity game changer, making it possible for Tinder to ship new features more quickly and be more confident about the changes we were making in production.