The challenge
At first, Paperlust configured their web shop on a single server that hosted both the applications and the databases. They soon outgrew this solution, though, as their user base expanded. Customers began to experience significant lag when using the site, leading to a poor customer experience. To alleviate performance issues, Paperlust decided to separate the applications and databases and moved their databases into a managed relational databases service.
This migration did not have the desired effect, and they had to move their database multiple times in efforts to conquer their performance problems. Each time this happened, they had to turn off the server and configure a new endpoint. This led to even more delays.
Waiting for an online shop for paper products to respond seems like a small thing, but it has big consequences for the company in question. Firstly, performance issues gradually reduce their site’s availability, leading to revenue loss and decline in customer trust.
Moreover, it’s wasting time internally. Development work grinds to a halt as the team waits for the server to run again. And this isn’t even taking into account the frustration it causes!
Paperlust were aware that they could tackle this issue by taking closer care of the database and adding some components. “But we thought it would add complexity to our stacks,” says Alex. “We didn’t really have a team to manage the infrastructure on a daily basis.