Node WebRTC Merge & Scale
Budget: ₹12,500 – ₹37,500 INR
I have a functioning calling platform built with Node.js and WebRTC, but it’s scattered across three separate folders. The split structure makes maintenance difficult and, more importantly, it is causing connection-related bugs that stop peers from reaching each other. My goal is to consolidate everything into a single, clean project, eliminate the connection problems, and tune the code so it can perform smoothly under heavier loads.
Here’s what I need from you:
• Diagnose and fix the current WebRTC connection issues—sessions occasionally fail to establish or drop mid-call.
• Refactor the existing codebase into one well-structured project (shared modules, clear build process, common dependencies).
• Optimise signalling, media handling, and any bottlenecks so the app scales efficiently and overall performance improves.
• Prepare a production-ready deployment workflow so I can push the site live as soon as the fixes are verified (Docker, PM2, or a process you’re comfortable with).
Experience with Node.js, Express, Socket.io (or a comparable signalling layer), and STUN/TURN configuration is essential. If you’ve already solved similar connection or scalability problems, please highlight that in your message—the more relevant your experience, the faster we can move.
I’m ready to test immediately and go live once the call flow runs reliably from start to finish. Looking forward to working with someone who can dive straight in and get this over the finish line.
Here’s what I need from you:
• Diagnose and fix the current WebRTC connection issues—sessions occasionally fail to establish or drop mid-call.
• Refactor the existing codebase into one well-structured project (shared modules, clear build process, common dependencies).
• Optimise signalling, media handling, and any bottlenecks so the app scales efficiently and overall performance improves.
• Prepare a production-ready deployment workflow so I can push the site live as soon as the fixes are verified (Docker, PM2, or a process you’re comfortable with).
Experience with Node.js, Express, Socket.io (or a comparable signalling layer), and STUN/TURN configuration is essential. If you’ve already solved similar connection or scalability problems, please highlight that in your message—the more relevant your experience, the faster we can move.
I’m ready to test immediately and go live once the call flow runs reliably from start to finish. Looking forward to working with someone who can dive straight in and get this over the finish line.
Related categories:
JavaScript
NoSQL Couch & Mongo
Node.js
VPS
Docker
API Development
Microservices
WebRTC