What 600k concurrent sessions taught me about Redis connections
Our Redis outages looked like a capacity problem. They weren't: every request was opening its own connection. Here's the multiplexing fix that kept the Mixx Tanzania app up at peak.
In the Mixx Tanzania app, every Redis call was opening its own connection. At peak that went past the connection limit and caused downtime, so I replaced it with one shared, multiplexed connection.
Pick a step to replay it
Each request created a new Redis connection. During peak traffic, with 600k+ concurrent sessions, the connection count went past the limit, causing timeouts, runtime errors, and downtime in the Mixx Tanzania app.
Stack.NET, Redis and Connection multiplexing
Our Redis outages looked like a capacity problem. They weren't: every request was opening its own connection. Here's the multiplexing fix that kept the Mixx Tanzania app up at peak.
Automated CI/CD for the telco agent apps with Docker and Jenkins. The image signed off in UAT on PreProd is the exact image that goes to production, under a new tag, which cut deployment errors by 99%.
Built withDocker, Jenkins, CI/CD and .NET
Read case studyOpen to full stack, product & backend roles.