How Redis broke our application
summary
A Laravel deployment switched queue driver from the database to Redis and broke job references because Redis uses alphanumeric job IDs while the MySQL jobs table expects integer IDs, causing truncated foreign keys and inconsistent notifications. The migration involved opening the Redis port and configuring it, but tests and staging didn’t run against Redis so the bug was missed; the concrete fixes are to run tests on multiple drivers and avoid putting business logic into infrastructure.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 9:00What could have happened?
- 15:00Why didn’t we notice?
- 18:00Laravel is a fantastic framework
- 21:00You shouldn’t mix these two things
- 23:00Testing on multiple drivers
- 26:00Abstraction
- 29:00Questions
related talks
34mScaling Redis writes with cluster mode
10mRedis, databaza në memorie me shumë përdorime
01h 02mBreak Out of Redis
46mFun with Ruby and Redis
56mRedis Application Patterns in Rails
20mhow to make the management of a league system less traumatic
34mBeyond CRUD: the PostgreSQL techniques your Rails app is missing.
14mMigrating 15k Redis servers to Valkey