Support and Maintenance en Milan
How we work in Milan
What gets worse gradually sets off no alarm
A listing that took half a second two years ago and takes four today has never gone down, so nobody has reported it. The catalogue has grown and the index that used to do the job no longer does. We record the timings of the critical queries month by month to see it coming before the person buying does.
The nightly load is watched like the website
If the price and stock synchronisation does not finish, the alert has to arrive on its own, with the time and the reason. Without that, the failure is discovered mid-morning because somebody notices an out-of-stock item still on sale. Checking only whether the site responds leaves out half of what can break.
Additions and removals are maintenance too
Getting a withdrawn item to disappear the same day from the filters, the internal search and the ads file does not happen by itself: they are three different systems, each with its own copy of the data and its own refresh rhythm. In a live catalogue, keeping them aligned is continuous work and not a launch task.
The campaign peak is prepared, not improvised
Big days multiply the traffic precisely on the pages that are most expensive to serve, which are the filtered listings. They are tested beforehand with simulated load on an environment identical to the real one, and you decide what can be cached and what cannot. Finding the limit on campaign day is the most expensive way to find it.
Answering your questions
What people ask us about Support and Maintenance in Milan.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs