u/Positive_Roof5591

Hi, I am — a backend-focused full stack developer with experience building scalable SaaS platforms, real-time systems, dashboards, and production backend infrastructure.

What I can help with:

Node.js / Express APIs

Backend architecture & system design

MongoDB / PostgreSQL optimization

WebSockets / real-time systems

AWS / Docker deployments

SaaS platforms & dashboards

Payment integrations

API integrations & automation

Recent work:

Built backend infrastructure for a cab booking platform serving 5,000+ users

Developed real-time marketplace/chat systems

Built a WebRTC-based remote support platform with Dockerized deployment

Tech stack:
Node.js, Express, React, Next.js, MongoDB, PostgreSQL, Redis, AWS, Docker, TypeScript

Rate:
$15/hr (flexible for long-term work)

Remote friendly.

DM me if you’re looking for backend/full stack help.

Hi, I’m a Full Stack Developer with experience building scalable SaaS platforms, real-time systems, dashboards, and backend-heavy applications.

What I can help with:

• Full Stack Web Apps
• Node.js / Express APIs
• React / Next.js Frontends
• Real-Time Systems (WebSockets / Socket.IO)
• SaaS Platforms & Dashboards
• MongoDB / PostgreSQL
• AWS / Docker Deployment
• Payment Integrations

Recent work:

• Built backend infrastructure for a live cab booking platform serving 5,000+ users
• Developed real-time chat & marketplace systems
• Built a WebRTC-based remote support platform with Dockerized deployment

Tech Stack:
Node.js, React, Next.js, MongoDB, PostgreSQL, AWS, Docker, TypeScript

Rate:
$15/hr (flexible for long-term work)

Portfolio:
Available in profile / DM

Contact:
DM me if you’re building something interesting.

While working on a real-time app with Socket.IO, I realized changing a user’s password didn’t invalidate their already-connected socket sessions.

So even after password reset, existing live connections could stay active.

What fixed it:

Reject new socket connections using tokens issued before passwordChangedAt

On password change, loop through that user’s active socket IDs, emit forceLogout, then disconnect them immediately

Result:

old sockets disconnected instantly

old tokens fail on reconnect

password change truly logs out everywhere

Curious how others handle session invalidation in real-time apps.

While building a location-based task feed, indexing reduced our response time by ~60%. Curious what indexing wins others have seen in production.