Moving from a monolith to microservices in 2014 “solved a problem on the development side, but it pushed that problem to the infrastructure team,” says Kevin Lynch, Staff Engineer on the Site Reliability team at Squarespace. “The infrastructure deployment process on our 5,000 VM hosts was slowing everyone down.”
The team experimented with container orchestration platforms, and found that Kubernetes “answered all the questions that we had,” says Lynch. The company began running Kubernetes in its data centers in 2016.
Since Squarespace moved to Kubernetes, in conjunction with modernizing its networking stack, deployment time has been reduced by almost 85%. Before, their VM deployment would take half an hour; now, a templated application can be generated and deployed in five minutes. Because of that, “productivity time is the big cost saver,” he adds. “When we started the Kubernetes project, we had probably a dozen microservices. Today there are twice that in the pipeline being actively worked on.” Resilience has also been improved with Kubernetes: “If a node goes down, it’s rescheduled immediately and there’s no performance impact.”
CNCF projects used
Reduced by 85%
Number of microservices
Containerized, templated applications can be deployed in 5 minutes
Since it was started in a dorm room in 2003, Squarespace has made it simple for millions of people to create their own websites.
Behind the scenes, though, the company’s monolithic Java application was making things not so simple for its developers to keep improving the platform. So in 2014, the company decided to “go down the microservices path,” says Kevin Lynch, staff engineer on Squarespace’s Site Reliability team. “But we were always deploying our applications in vCenter VMware VMs [in our own data centers]. Microservices solved a problem on the development side, but it pushed that problem to the Infrastructure team. The infrastructure deployment process on our 5,000 VM hosts was slowing everyone down.”
After experimenting with another container orchestration platform and “breaking it in very painful ways,” Lynch says, the team began experimenting with Kubernetes in mid-2016 and found that it “answered all the questions that we had.” Deploying it in the data center rather than the public cloud was their biggest challenge, and at the time, not a lot of other companies were doing that. “We had to figure out how to deploy this in our infrastructure for ourselves, and we had to integrate it with our other applications,” says Lynch.
At the same time, Squarespace’s Network Engineering team was modernizing its networking stack, switching from a traditional layer-two network to a layer-three spine-and-leaf network. “It mapped beautifully with what we wanted to do with Kubernetes,” says Lynch. “It gives us the ability to have our servers communicate directly with the top-of-rack switches. We use Calico for CNI networking for Kubernetes, so we can announce all these individual Kubernetes pod IP addresses and have them integrate seamlessly with our other services that are still provisioned in the VMs.”
Within a couple months, they had a stable cluster for their internal use, and began rolling out Kubernetes for production. They also added Zipkin and CNCF projects Prometheus and fluentd to their cloud native stack. “We switched to Kubernetes, a new world, and we revamped all our other tooling as well,” says Lynch. “It allowed us to streamline our process, so we can now easily create an entire microservice project from templates, generate the code and deployment pipeline for that, generate the Docker file, and then immediately just ship a workable, deployable project to Kubernetes.” Deployments across Dev/QA/Stage/Prod were also “simplified drastically,” Lynch adds. “Now there is little configuration variation.”
And the whole process takes only five minutes, an almost 85% reduction in time compared to their VM deployment. “From end to end that probably took half an hour, and that’s not accounting for the fact that an infrastructure engineer would be responsible for doing that, so there’s some business delay in there as well.”
With faster deployments, “productivity time is the big cost saver,” says Lynch. “We had a team that was implementing a new file storage service, and they just started integrating that with our storage back end without our involvement”—which wouldn’t have been possible before Kubernetes. He adds: “When we started the Kubernetes project, we had probably a dozen microservices. Today there are twice that in the pipeline being actively worked on.”
“Once you prove that Kubernetes solves one problem, everyone immediately starts solving other problems without you even having to evangelize it.”— KEVIN LYNCH, STAFF ENGINEER ON THE SITE RELIABILITY TEAM AT SQUARESPACE
There’s also been a positive impact on the application’s resilience. “When we’re deploying VMs, we have to build tooling to ensure that a service is spread across racks appropriately and can withstand failure,” he says. “Kubernetes just does it. If a node goes down, it’s rescheduled immediately and there’s no performance impact.”
Another big benefit is autoscaling. “It wasn’t really possible with the way we’ve been using VMware,” says Lynch, “but now we can just add the appropriate autoscaling features via Kubernetes directly, and boom, it’s scaling up as demand increases. And it worked out of the box.”
For others starting out with Kubernetes, Lynch says his best advice is to “fail fast”: “Once you’ve planned things out, just execute. Kubernetes has been really great for trying something out quickly and seeing if it works or not.”
“Kubernetes allowed us to streamline our process, so we can now easily create an entire microservice project from templates.”— KEVIN LYNCH, STAFF ENGINEER ON THE SITE RELIABILITY TEAM AT SQUARESPACE
Lynch and his team are planning to open source some of the tools they’ve developed to extend Kubernetes and use it as an API itself. The first tool injects dependent applications as containers in a pod. “When you ship an application, usually it comes along with a whole bunch of dependent applications that need to be shipped with that, for example, fluentd for logging,” he explains. With this tool, the developer doesn’t need to worry about the configurations.
Going forward, all new services at Squarespace are going into Kubernetes, and the end goal is to convert everything it can. About a quarter of existing services have been migrated. “Our monolithic application is going to be the last one, just because it’s so big and complex,” says Lynch. “But now I’m seeing other services get moved over, like the file storage service. Someone just did it and it worked—painlessly. So I believe if we tackle it, it’s probably going to be a lot easier than we fear. Maybe I should just take my own advice and fail fast!”