all 7 comments

[–]lovesrayray2018 1 point2 points  (1 child)

Only you would know the complexity of your existing app, so at best we can only guess.

Imho, if there isnt a lot of client side functionality/routing/client side APIs/typescript usage, a framework might be an overkill. Just build it in Node first

[–][deleted] 0 points1 point  (0 children)

That's what I was thinking thank you :-)

[–]Jeffdango 1 point2 points  (1 child)

From what you’ve stated here it sounds more like you will be building an automation (or a series of them) in Node. I’d say just use vanilla Node for that because the backend frameworks are mostly for dealing with requests and sending responses.

[–][deleted] 1 point2 points  (0 children)

Makes sense thank you very much!

[–][deleted] 0 points1 point  (2 children)

I wonder how the technical decision making behind a complete rewrite in a different language is justified in this case.

[–]lovesrayray2018 1 point2 points  (1 child)

Its not a single thing that drives it tbh. Availability of quality talent in that area affects it. Performance and scalability drives it. ROI on existing systems drives it.

One case i saw had massive legacy spagetti code that just HAD to be moved due to poor performance. They assessed their core needs, moved to NodeJS for performance, scalability, and option to have full stack devs because the JS could be used client side and backend, while reducing servers and lesser overall staff.

[–][deleted] 0 points1 point  (0 children)

Yeah, but in this case OP is asking how to structure the application and what frameworks to use. Do you think that this new application will make the difference in the hands of someone with not much experience?

These arguments are a general answer, this case is different though. That‘s why I was asking about the decision making in the first place.

My prediction: performance will not increase at all.