Tell me about the request routing service with configuration from the database. What kind of configurations are these? How did the hot loading work?

In the request routing service with configuration from the database, the main idea is to store routing rules in the database so that it is possible to flexibly manage the request distribution logic without recompiling and restarting the service.

Configurations usually include:

• Request filtering rules by parameters (request type, priority, region, etc.)
• Rules for assigning performers or groups
• Priorities and fallback scenarios
• Time conditions (e.g., working hours)

Hot loading means that the service periodically or upon an event reads the current configurations from the database and updates internal data structures without stopping. This is implemented through:

• A caching mechanism for configurations in memory
• Timers or change listeners in the database (e.g., triggers or notifications)
• Atomic replacement of configurations at runtime to avoid race conditions

This approach allows quick response to changes in business logic and minimizes downtime.