You may have read that recently we rebranded our flagship product, Intranet DASHBOARD (iD), to GreenOrbit. As with all rebrands, a new marketing website was required and the obligatory discussion about the tech stack we should use was had.
The outgoing iD website had been built a number of years ago in .NET, sat on some servers behind a load balancer and connected to a database for some of the functionality. It worked and by all means wasn’t slow, but it wasn’t all that fast either.
Along with the usual requirements of being easy to update, templated layouts for expandability, integration with our CRM, secure, highly available, fault tolerant and scalable, it also had to be seriously fast. The experience needed to be the same for everyone no matter where in the world our visitors were from.
I’m a big fan of serverless architectures and JAM stack — this was the path I wanted to take as I knew we’d be able to achieve our goals using these methods. The problem I faced was the team I was working with were relatively new to developing sites this way, and were nervous about meeting the relatively tight timeframes we had in place.
One of our values at GreenOrbit is to be adventurous, so the team accepted the challenge and dived right in.
