Node.js Realtime API Development
Budget: ₹1,500 – ₹12,500 INR
I’m building a standalone API and have settled on Node.js for the backend. The service must handle user authentication, persistent data storage, and real-time updates from the outset, so I need someone who is comfortable weaving all three together without bolting them on as after-thoughts.
Here is what I expect from you:
• Clean, well-documented Node.js code (TypeScript welcome if that’s your style).
• Secure authentication flow (JWT or OAuth2 are both fine so long as tokens can be easily refreshed).
• A database layer that scales—PostgreSQL is my default, but I’m open to MongoDB or another engine if you can justify the fit.
• Real-time messaging via WebSocket, Socket.IO, or a comparable solution that plays nicely with load-balanced environments.
• Clear API documentation (OpenAPI / Swagger) so any front-end or third-party team can plug in immediately.
• A short deployment guide—Docker-compose is perfect, a Kubernetes chart is even better.
Acceptance criteria:
1. All authentication routes must pass automated tests for sign-up, login, token refresh, and role-based access.
2. CRUD endpoints for the main data models respond within 200 ms under moderate load (I’ll provide test cases).
3. Real-time events broadcast correctly to subscribed clients and survive a server restart without data loss.
4. README and Swagger JSON render without errors on the first clone.
If this sounds like a challenge you enjoy, let’s talk about timelines and milestones.
Here is what I expect from you:
• Clean, well-documented Node.js code (TypeScript welcome if that’s your style).
• Secure authentication flow (JWT or OAuth2 are both fine so long as tokens can be easily refreshed).
• A database layer that scales—PostgreSQL is my default, but I’m open to MongoDB or another engine if you can justify the fit.
• Real-time messaging via WebSocket, Socket.IO, or a comparable solution that plays nicely with load-balanced environments.
• Clear API documentation (OpenAPI / Swagger) so any front-end or third-party team can plug in immediately.
• A short deployment guide—Docker-compose is perfect, a Kubernetes chart is even better.
Acceptance criteria:
1. All authentication routes must pass automated tests for sign-up, login, token refresh, and role-based access.
2. CRUD endpoints for the main data models respond within 200 ms under moderate load (I’ll provide test cases).
3. Real-time events broadcast correctly to subscribed clients and survive a server restart without data loss.
4. README and Swagger JSON render without errors on the first clone.
If this sounds like a challenge you enjoy, let’s talk about timelines and milestones.