I started working in Node.js backend deployed in an EC2 instance, then suddenly i was asked to move to LAMBDA in AWS. I didn't want to refactor all the code again so I did the same thing and everything has worked ok so far, although we are not in production yet. However I started breaking the API in a "entity or model basis" so at the end i will have 9 or 10 smaller lambda functions proxied through the same API GATEWAY ... but at the end the thing is you can keep coding as usual, even you can test locally an then test in AWS as you said ...
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.
Hello Tal,
I started working in Node.js backend deployed in an EC2 instance, then suddenly i was asked to move to LAMBDA in AWS. I didn't want to refactor all the code again so I did the same thing and everything has worked ok so far, although we are not in production yet. However I started breaking the API in a "entity or model basis" so at the end i will have 9 or 10 smaller lambda functions proxied through the same API GATEWAY ... but at the end the thing is you can keep coding as usual, even you can test locally an then test in AWS as you said ...