ScuolaZoo: a high-traffic ecosystem kept standing all year

A digital ecosystem that holds through entire seasons is not a project that ends: it is a commitment that continues. ScuolaZoo has a wide one, holding together the app, the website, the portal, the travel planner and the back offices underneath. And it is an ecosystem that lives on peaks: when trip bookings open, traffic does not grow, it spikes. Then there is the rest of the year, when the same platforms simply have to work.

For several months we have looked after them with continuous, ordinary maintenance across the whole estate: tickets taken on one by one, faults fixed, updates released, production systems monitored. It is the work that never makes the cover, and it is the work that decides whether everything else holds: on platforms like these, the difference between a peak absorbed and a peak suffered is built in the quiet months.

Meanwhile the product keeps evolving, and the place it evolves most is the checkout. There we design and build new features on the purchase and booking flows, grafting them onto systems that are already running: no downtime window, because a checkout that goes dark is not a technical inconvenience, it is revenue that does not arrive.

The team is small and stable. A project manager coordinates the work, holds the relationship with the client and plans the developers' windows. A tech lead oversees architecture and the CI/CD pipeline and reviews what goes out. A mobile developer looks after the app, a full stack developer the front end and backend of the web platforms, the travel planner, the back office and the new checkout features. The same people, month after month: on a system you did not write yourself, accumulated knowledge is half the job.