Puppeteer, Proxy configuration: troubleshooting and migration to Lambda.

Using Node.js, I want you to help me troubleshoot and optimize code written to provide an API that will leverage Node.js, and Puppeteer to retrieve web pages.

We have a few bugs that we need to resolve. Then, from there, we need to make some improvements, such as adding multiple TOKEN/Keys for access.

Bug to fix:
1) After about 10 requests, the node.js server stops with a potential memory leak. Ive hacked it by setting sessions to infinity. But, there needs to be a better solution.
2) Occasionally, after about 40 requests, we get a big crashing error that is unhandled.
3) We also seem to timeout occasionally.
4) And lastly, occasionally, we get a tunnel connect error.

After these bug fixes, and things are operational, Id like to move this to AWS Lambda, OR a Docker-based setup, or other FaaS provider, so we can scale this up a bit.

Looking to move on this now. If youre a good, longer term player, wed love to start here, and then continue on with other occasional jobs. My goal is to move eventually ALL the parsing into this library server so we can eliminate it from the Ruby app that connects to it.
About the recuiter
Member since May 20, 2018
Azza Rul
from Bas-Rhin, France

---

---

Looking for help? Checkout our video tutorial
How to search and apply for jobs

How to apply? Do you have more questions about the Job?
See frequently asked questions