What were the RPS on the ticketing project services?

The specific RPS (requests per second) values on ticketing project services depend on the architecture, load, and time of day, but generally, the following ranges are typical:

• Main frontend service: from a few hundred to several thousand RPS during peak hours.
• Ticket search services: can reach several thousand RPS, as database and external API requests are intensive.
• Booking and payment services: usually have lower loads, around hundreds of RPS, but require high reliability and low latency.

For an exact answer, it is necessary to look at the metrics of the specific project, but overall, RPS on ticketing services range from hundreds to several thousand depending on functionality and time.