I will build realtime features with websockets, redis and rabbitmq


About this gig
Real time is where backends usually break. A socket server that works for ten users falls over at a thousand, messages arrive twice, and nobody notices until a customer complains.
I am a senior backend engineer and this is the part of the stack I spend most of my time in. I build live features that survive reconnects, restarts and scale out across more than one server.
What I build:
WebSocket services with rooms, authentication and presence, in Node.js or NestJS
Redis pub sub so your sockets keep working when you run more than one instance
RabbitMQ queues with workers, retries, dead letter handling and backpressure
Live dashboards, chat, notifications, order and status feeds
Event driven services that stay consistent when a job fails halfway
Load testing with k6 so you know the real limit before your users find it
I also fix existing setups: dropped connections, duplicated events, memory that grows until the process dies, queues that silently stall.
You get clean source, the config, and a short note on how it behaves under load and what to watch.
Tell me what should update live and how many people will be connected, and I will tell you what it needs.
Get to know Vishal Sainani
Senior Backend Engineer for AI Voice and Real Time Systems
- FromPakistan
- Member sinceOct 2026
Languages
Urdu, Sindhi, English
Other Software Development Services I Offer
FAQ
Will this work if I run more than one server?
Yes. That is exactly what the Redis pub sub layer is for. Without it a message sent on one instance never reaches clients connected to another, which is the most common real time bug I get asked to fix.
Do you build the frontend part too?
I build the server side and give you a working client example in React or plain JavaScript so your team can wire it into the UI. Full UI work is possible but we should agree the scope first.
Can you fix my existing WebSocket setup instead of rebuilding it?
Yes, and that is often cheaper. Send me the repo and describe what goes wrong. I will tell you whether it is a fix or a rebuild before you order.
How many concurrent users can it handle?
It depends on your message rate and payload size, so I will not quote a number blind. On the Premium package I load test it with k6 and give you the measured figure for your own setup.
