
In Progress
Posted
I run a Svelte web-app that streams live readings from user-owned sensors. Each time a new sensor is registered the backend writes a user-to-device mapping into Redis; this mapping is then used to route all subsequent messages. Right now the Redis part is failing. The web-app itself loads, the registration call completes, and a key does appear in Redis, yet the association is not updated correctly so the new sensor’s traffic never reaches the UI. In short, the Redis server is the bottleneck and it isn’t updating with new sensors as expected. What I need from you: • Trace and fix whatever in Redis (key pattern, Lua script, TTL, race condition, Pub/Sub channel, etc.) is preventing a clean update when a sensor is added. • Prove the fix by registering multiple new sensors and showing their data flowing through to the Svelte front-end in real time. • Hand over the patched code or configuration plus a short summary of the root cause and the changes made. If you’re comfortable debugging Redis (stand-alone instance, not clustered) and can work smoothly alongside a Svelte/Node stack, this should be a focused task. I’m ready to get the patch merged and live as soon as the routing is rock-solid again.
Project ID: 40261945
62 proposals
Remote project
Active 4 mos ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs