EdPayU familyFamily homeEdPayU+ — you are hereEdPayU · the school app →
Scale

Result day is the
design load.

Education traffic is not average traffic. It is every parent at once, four times a year, at the exact moments that matter most. A platform that merely handles the average has already failed the year.

The engineering rules

Rules the code enforces,
not intentions it hopes.

No unbounded reads

  • Every list pages from its first version — nothing loads “all students”
  • Every query carries a bound; the ceiling is a build rule, not a hope
  • A 40,000-student group hits the same screens as a 400-student school

No small-tenant assumptions

  • Designed against a target of a million users on the platform
  • Screens are reviewed against the largest tenant, not the demo tenant
  • Group structures — one trust, many branches — are first-class, not a loop

Peaks are scheduled

  • Result publication, fee deadlines and admission opens are known in advance
  • The read paths those days hammer are cached deliberately, not accidentally
  • Messaging bursts queue and drain; they do not stampede the database

The days that matter

Load across an institution's yearAn illustration of relative load, not measured traffic. Demand is flat on ordinary days and spikes sharply on the fee due date, result day and the opening of admissions. The system is sized for those peaks, not for the average.OrdinarydayFeedue dateOrdinarydayResultdayOrdinarydayAdmissionopen
Relative shape, not measured traffic. Capacity is not sized for the average day — it is sized for result day and the fee deadline, when every family opens the same page at once.

Why this is a buying criterion

Every ERP works in the demo. The year finds out which ones work in March.

The failure mode of institution software is seasonal. A system that ran fine through July collapses on the morning results publish, because every family opens the app inside the same ten minutes; or on the last day of the fee concession, because every payment and every receipt lands together; or on the day admissions open, because a good school’s form gets more traffic in an hour than its website sees in a quarter. These are not surprises. They are printed in the academic calendar, and software for this market should be engineered against them by name.

That is what the rules above are for. Bounded reads and mandatory paging are not performance tuning — they are the guarantee that no screen, anywhere, degrades with tenant size, which is what lets one platform serve a coaching centre and a hundred-branch group without either subsidising the other. We publish the rules rather than a benchmark because a benchmark is a number from our machine, and the rules are checkable behaviour on yours: open the biggest list you have in the demo and watch it page.

Bring your

Your student count, your result-day pattern, your branch structure — we run the session against it.

Chat with us