Help on decision of using Indico

1

Hello everyone,

First of all, thank you for all the support and for the valuable discussions shared in this forum. I would also like to apologise in advance if this is not the appropriate place to raise the questions I am about to ask.

I am currently assessing whether Indico is the right platform for an event organised by my university. The event runs for one full week and is divided into several parallel programmes. Each participant may register for only one programme, and each programme has a limited number of seats. Registrations are processed strictly on a first‑come, first‑served basis.

Another important requirement is that a registration should only be considered valid after the corresponding payment has been completed.

We are expecting a very high level of demand, with more than 500 people likely to attempt to register at the same time. Because of this, I would like to understand whether Indico is capable of handling this type of workload and registration logic, or whether additional modules or custom development might be required.

Any guidance, recommendations, or examples from similar use cases would be greatly appreciated.

Thank you in advance for your help!

2

Hi, should be fine, but of course it also depends on your deployment. If you run it on a tiny VM you might encounter some slowness, while if you run it on something more beefy (and thus have more uwsgi worker processes that can handle requests) it may be better.

It is not possible to make a registration only count against the registration limit after payment. You need to manually remove registrations still unpaid after whatever duration you want to give people to pay.

1 Like
3

Does the platform implement any internal concurrency‑control or queuing mechanisms—such as transactional locks, atomic counters, or serialized request handling—to prevent race conditions that could otherwise result in oversubscription when multiple users attempt to register simultaneously for a limited‑capacity programme?

4

No, we do not have specific logic for this. However, we have never encountered issues w/ excessive registrations.

1 Like