I moved from Laravel to Node, and it was not exactly joyful. I was/am using AdonisJS - feels like Laravel in Node world, so the migration was a bit easier.
IMO Laravel has quite a bit of tools + articles + people who were making development easier. Node + Javascript has a huge community but one tends to get confused by the many options.
Looking back: I should have probably moved something small, evaluated how we fare and incrementally take up more. I will certainly not take up more complexity at the beginning - for e.g. move to a headless CMS + GraphQL while I was in Laravel + the good ol' Rest.
Then - there is also a matter of cost. Shared servers can run Laravel and cost next to nothing while being acceptable for smaller applications. NodeJS on low-end VPS is not exactly expensive but things tend to add up. If you are in this situation - be mindful of the ongoing maintenance (patching OS, web servers, etc.)
I’m a full stack engineer working at Numu, in charge of developing web and mobile apps, handling AWS applications and devOps tasks. I may also write sporadically about my technical adventures.
Thanks for the reply. I have a big system that I want to move to NestJS. I have a website in Gatsby, 3 web portals and a RN app.
Everything including the database is hosted on AWS and I need to be able to scale. Also I love Laravel its a great framework you're right about the support and articles but it isn't really known to be performant at scale.
That, along with the fact that devs here run from PHP and tend to go towards JS technologies is why I'm considering moving to NestJS.
I do like the idea of porting something small. I had the exact same idea in mind about porting the portal we use for in-house use.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't have a lot to say, but here goes -
I moved from Laravel to Node, and it was not exactly joyful. I was/am using AdonisJS - feels like Laravel in Node world, so the migration was a bit easier.
IMO Laravel has quite a bit of tools + articles + people who were making development easier. Node + Javascript has a huge community but one tends to get confused by the many options.
Looking back: I should have probably moved something small, evaluated how we fare and incrementally take up more. I will certainly not take up more complexity at the beginning - for e.g. move to a headless CMS + GraphQL while I was in Laravel + the good ol' Rest.
Then - there is also a matter of cost. Shared servers can run Laravel and cost next to nothing while being acceptable for smaller applications. NodeJS on low-end VPS is not exactly expensive but things tend to add up. If you are in this situation - be mindful of the ongoing maintenance (patching OS, web servers, etc.)
Thanks for the reply. I have a big system that I want to move to NestJS. I have a website in Gatsby, 3 web portals and a RN app.
Everything including the database is hosted on AWS and I need to be able to scale. Also I love Laravel its a great framework you're right about the support and articles but it isn't really known to be performant at scale.
That, along with the fact that devs here run from PHP and tend to go towards JS technologies is why I'm considering moving to NestJS.
I do like the idea of porting something small. I had the exact same idea in mind about porting the portal we use for in-house use.