- React 16 mobile-first frontend
- Apollo GraphQL for the API
- All code is Typescript
- Static content is hosted on CDN.
- Progressive Web Application
Why custom NodeJS not PHP?
With over 10yrs of PHP experience I know it doesn’t scale well. The typical answer is to throw hardware & money at the performance issues. This usually means bigger servers that have to cope with the biggest possible demand adding caching systems in front of the servers and more. Some ISPs offer optimal solutions for Magento to support their high demands.
By example, in terms of scalability of LinkedIn’s mobile backend infrastructure: the company was able to move from 30 servers down to just three, while still having enough headroom to handle roughly ten times their current level of resource utilisation when they decided to switch to Node.js. There’s been a lot of talk about PayPal moving from Java to Node.js for an application platform. The Node.js app was built almost twice as fast with fewer people, written in 33% fewer lines of code, constructed with 40% fewer files.
NodeJS (blue) vs PHP (orange) performance at scale, lower = better.
Faster response = better user experience & lower running cost
Better user experience = higher revenue
React runs on the customers’ device and only request small amounts of data from the servers as required. It gives an “application like” experience on the web.
The customer benefits from faster response times due to these small requests.
The business benefits as much of the data processing is done by the customers, reducing load & costs on the servers.