Scalable Microservices Architecture

At WP.one, we started to have a lot of users - being over 500K and counting. But as more people started using it, our legacy system began to struggle. It was slow in making new installations, and when lots of users were online at the same time, things weren't looking so nice. The setup we had was too old-school and couldn’t handle the pressure, which made it hard to add new features or make changes.

The main goal was to fix the system so it could handle more users without slowing down, especially when creating new sites, which was important for keeping users happy and helping the business grow. We needed a complete makeover of the system that runs the website to make this happen.

So, we decided to break our big, clunky system into smaller, independent parts using something called a microservices architecture. We chose NestJS, a framework for building these parts because it’s really good at organising architecture, code and making sure everything runs smoothly. We also used TCP, a way for these parts to talk to each other reliably, ensuring that messages don’t get lost in translation.

Making Sites Faster: By switching to this new setup, we cut the time needed to create new sites by half. This meant users could get their sites up and running much quicker, making everyone a lot happier.

Growing Without the Growing Pains: This new system was also a lot more flexible. It could easily adjust to more users coming on board, keeping the website running smoothly even during busy times. This was a game changer for WP.one because it meant they could keep growing without their system breaking down.

By getting rid of their old, bulky system and moving to a sleeker, more modern setup, WP.one made a huge leap forward. Sites were created faster, the system could handle more users, and overall, the platform got a lot better at serving its growing community. This story shows how using the right tech can really turn things around for a business.