Infrastructure 2.0 - Unleash
As Unleash grows our hosted offering, we’ve seen the need to automate what we have been doing with carefully crafted AWS scripts and manual effort. This blog post goes through our process and learnings in how we handle our infrastructure.
As of April 2022, what has been the result of a long 4 months of effort culminated in turning off the last EC2 instance. The biggest benefit has been that our new set-up allows us individual scaling of each customer based upon their needs and requirements. This blog post will not go into details about any specific customer but rather focus on the general setup.
This made it clear that we needed to change how we were doing deployments, we could no longer take the risk of our EC2 instances crashing or the owner of our scripts being unavailable.
Warning : The rest of this article will be technical in nature, the TL;DR: (too long; didn’t read:) is that we’ve migrated from manually controlled instances to a Kubernetes setup.
