I will build a real time chat or live updates feature with socketio

H
harsh8425
H
harsh8425
Harsh
build a real time chat or live updates feature with socketio
Full Screen
build a real time chat or live updates feature with socketio

About this gig

Most real-time features are easy to demo and hard to keep correct. The demo works. Then a phone switches from wifi to cellular, a user opens two tabs, or a second server instance appears, and suddenly people are seeing different versions of the truth.


I build the version that survives those things. Four years on production real-time platforms carrying thousands of concurrent connections, owned end to end.


WHAT YOU GET

Basic - One real-time feature on your existing backend: live updates, presence, or notifications. Reconnection handled properly. 4 days.

Standard - A full chat or live-collaboration feature: rooms, history, presence, typing indicators, delivery and read state, with state resync after a dropped connection. 8 days.

Premium - Standard plus multi-instance scaling with the Redis adapter, sticky sessions, and a load test at your expected concurrency. 14 days.


HOW IT WORKS

1. We agree the exact behaviour before I start, in writing.

2. You see working code at the halfway point, not only at the end.

3. Delivered as pull requests against your repo, with the architecture explained.

  • Website type

    • Business

  • Programming language

    • HTML & CSS
    • JavaScript
    • TypeScript
    • React
    • Bootstrap

  • Website features

    • Marketing
    • Payment
    • Forum
    • Social media
    • Inventory
    • Form
    • Map
    • Booking
    • Portfolio
    • Dashboard
Respect third-party rights

Please be aware that it is against Fiverr's policies for sellers to include themes, templates, or any other elements that infringe third-party rights or applicable laws in the delivered work. Read more about in our Guide to Responsible Digital Creation.

Get to know Harsh

Harsh

Real time backend engineer, Socket IO, Nodejs and Redis at scale

  • FromIndia
  • Member sinceOct 2020

  • Languages

    Hindi, English
I build and fix the real time layer most teams put off until it breaks: WebSocket systems that stay correct when thousands of users hit them at once. Four years running production systems end to end as the only engineer accountable for them, including real time multiplayer and iGaming platforms and multi tenant Node and PostgreSQL backends. Most real time failures are not bugs in the library. They are missing sticky sessions, no Redis adapter across instances, or reconnect logic that resubscribes forever. I find which one it is. Fixed scopes, agreed delivery dates.

Related tags