Hacker News new | past | comments | ask | show | jobs | submit login

We switched over from our old NodeJS backend to a new Go backend recently, and gave the website an overhaul as well, things were a bit shaky during the transition.



That NodeJS to Go definitely needs a write-up :-)


Any reason for the transition from the old NodeJS backend to the new Go backend? Did NodeJS hinder the performance in any way?


I wrote the old codebase ~4 years ago when I was just learning NodeJS, and didn't touch it too much after that, so it was in dire need of being replaced, in particular since it wasn't really written to scale horizontally.

Didn't have any particular issues with NodeJS in terms of performance, just felt like using Go when I was rewriting it.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: