← Home
Rustica: from AngularJS to Nuxt and Vue 3 on a live store

Rustica: from AngularJS to Nuxt and Vue 3 on a live store

Rustica makes custom doors and door hardware in the USA and sells them online. A customer doesn’t pick a product off a shelf: they build and customize a door on the site, then order what they built. The store takes orders around the clock, with NetSuite behind it.

As a senior developer at Devv.Co I maintained the old site, then led the team of three developers that rebuilt it. The rebuild started in November and went live in March, about four months later, and it still runs Rustica’s site today.

What we started with

The old site was built on AngularJS v1, integrated with NetSuite, with a Postgres database of its own. It had to keep working, with updates and bug fixes going out, for the whole time its replacement was being built.

There is no upgrade path from AngularJS v1 to Vue 3. Nothing carries over: not the components, not the templates, not the way state moves through a page. Getting to Vue 3 and Nuxt meant writing the store again, and it was a massive job.

What we rebuilt, and what we kept

  • The site, rewritten on Vue 3 and Nuxt.
  • The NetSuite integrations, rebuilt.
  • The Postgres database, kept. We improved it, but the changes stayed backward compatible.

The hard part: the data model we didn’t replace

The biggest headache was the original data model. On a rewrite the tempting move is to design the schema you wish you had. We couldn’t. So much had been built on the existing one that replacing it would have meant rebuilding everything that depended on it, on a store that was taking orders.

So we kept it and wrangled it. The new site had to do its job on top of a model designed for the old one, and we had to get really creative about how we worked around it. Where we improved it, each change had to leave everything that already existed working as before.

That constraint is also what made the launch safe. Because the database stayed the same, there was no data migration to get wrong on launch day, and the old site could stay up beside the new one.

Testing and the cutover

We tested it ourselves, and so did the business’s own employees. On top of that we hired outside user testers to do more QA than either group could.

The cutover itself had no trick to it. We planned it, kept the old site live, switched DNS to the new one and kept an eye out for issues. It went smoothly.

Tools

Vue 3 and Nuxt, rendered on the server, with Pinia for state and Tailwind for styling. NetSuite integrations and PostgreSQL behind it, Cloudinary for product images and CloudFront in front.