Improving the performance of a NodeJS server, a case study
I was given the task to upgrade a small NodeJS server nobody touched in years, and also see if I could do anything about its slow response time to (especially concurrent) requests.
I was given the task to upgrade a small NodeJS server nobody touched in years, and also see if I could do anything about its slow response time to (especially concurrent) requests.
PHP upgrade doesn't always have to be a pain, in this case it was not the codebase that posed a challenge. On the contrary, it was fairly easy to identify what needed to be changed in the code to get it ready for the upgrade. The problem was a custom extension we had to upgrade and recompile, and the restrictions of the pipeline. Here is how I solved the problem.
On this project, we had to reduce the time it took for a background job to deliver downloadable content for the client. The existing message queue solution - RabbitMQ - was not ideal for this, so we had to look for an alternative queuing solution.