3 ms·
Very well written. - I have nodejs server for the APIs and its running on m5.xlarge instance. I haven't done much research on what instance type should I go fo
by 120bits 5y ago
Very well written.
- I have nodejs server for the APIs and its running on m5.xlarge instance. I haven't done much research on what instance type should I go for. I looked up and it seems like c5n.xlarge(mentioned in the article) is meant compute optimized. That cost difference isn't much between m5.xlarge and c5n.xlarge. So, I'm assuming that switching to c5 instance would be better, right?
- Does having ngnix handle the request is better option here? And setup reverse proxy for NodeJS? I'm thinking of taking small steps on scaling an existing framework.
- talawahtech 5y agoThanks! The c5 instance type is about 10-15% faster than the m5, but the m5 has twice as much memory. So if memory is not a concern then switching to c5 is both a little cheaper and a little faster. You shouldn't need the c5n, the regular c5 should be fine for most use cases, and it is cheaper. Nginx in front of nodejs sounds like a solid starting point, but I can't claim to have a ton of experience with that combo.
- deleted 5y ago[deleted]
- nodesocket 5y agom5 has more memory, if you application is memory bound stick with that instance type. I'd recommend just using a standard AWS application load balancer in front of your Node.js app. Terminate SSL at the ALB as well using certificate manager (free). Will run you around $18 a month more.
- danielheath 5y agoFor high level languages like node, the graviton2 instances offer vastly cheaper cpu time (as in, 40%). That’s the m6g / c6g series. As in all things, check the results on your own workload!