Urgent.News

What's breaking now, across thousands of outlets.

Tech

Building a Waitlist with Automatic Promotion in Spring Boot (and Keeping the Queue Gap-Free)

🇺🇸 English version (🇧🇷 versão em português logo abaixo) The problem: sessions with limited spots I'm building a tutoring management system with Java, Spring Boot and PostgreSQL. Students can become tutors for a subject, and tutors open sessions with a limited number of spots. That raised a real business question: what happens when a session is full? I didn't want to just return "Session is…

The challenge lies in sessions that have a limited number of spots. In the tutoring management system built using Java, Spring Boot, and PostgreSQL, students can become tutors for a subject and open sessions with a limited number of spots. This led to the question of what happens when a session is full. The reporter wanted an optional waitlist feature, which allows students to be added to a queue if there are no spots available.

The first student in line gets promoted automatically when a confirmed student cancels, and the queue is renumbered without any gaps.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

What Is d3kOS?

The Marine Operating System Built for the Future Your phone has an operating system. So does your laptop, your car's infotainment screen and your TV. Boats are the exception.

  • d3kOS is an open-source marine operating system for recreational boats.
  • It runs on Raspberry Pi and integrates navigation, engine, and safety systems.
  • Features include AI navigation assistant, engine dashboard, and voice control.

An Annual Renewal Fails Once a Year. That's Exactly Why It Hurts.

Most billing dashboards are built around the monthly renewal. It happens twelve times a year, it fails at a fairly steady rate, and the recovery work is spread thin enough that no single failure feels…

  • Annual renewals cause larger, single charges disrupting monthly billing routine
  • Failed annual charges often trigger fraud controls, unlike monthly charges
  • Effective recovery requires dedicated calendar, staff, and metrics for annual renewals

How to Retry Email API Calls in Go: Backoff for Signup Verification

Short answer: Use a bounded exponential retry policy for failed email API calls: start at 2 seconds, cap the delay at 32 seconds, stop after 5 attempts, and make every attempt idempotent.

  • Ensure each API call attempt remains idempotent and log every retry attempt
  • Handle retryable rate limits and server failures while surfacing other terminal responses for review

More from Sunday 1 November →