Menu

The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams
📰

The rate limiter that checked the database first: how rejected requests kept 2,100 students out of their exams

DEV Community: database·Kashif Manzer·about 15 hours ago
#A9prGpL3
#devtodatabase#devto#dev#database#burst
Reading 0:00
15s threshold

On Tuesday 21 October 2026, at 12:18 in the afternoon, exams were about to start at several schools and colleges. Students sat down, opened their exam, and nothing happened. The start button did nothing, or the page never loaded. Three institutions were affected, up to 2,100 students in total, and for 19 minutes nobody at those institutions could start an exam.

The day before, the same thing had happened to one institution, for 13 minutes. A restart fixed it. On the Tuesday, the team restarted the servers twice. Nothing changed. The service came back only when they changed how the servers connected to the database.

Schoolyear is the platform those students use to take exams. Schools run exams on it, students start their exams through it, and supervisors open a dashboard to watch over them. Other assessment platforms connect to it too, sending requests on behalf of their own users.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.