Support and Maintenance en Lisbon
How we work in Lisbon
A useful alert fires before the error, not with it
By the time the system is returning a 500, the warning is late: your customer saw it before you did. Alerts that work watch the trend — requests queueing, response time climbing, memory that never comes back down — and fire while there is still room to act. It is a difference of ten minutes, and almost everything depends on those ten minutes.
What gets switched off first, decided in the cold
If the system cannot serve everything, giving up part of it beats going down entirely. Internal search, recommendations or reports can be disabled for an hour so that checkout stays alive. That list is written with you and written early, because it is a business decision dressed up as a technical one.
The bad day leaves the best information of the year
The logs from a spike show exactly what broke first, in what order and under how much load. It is information you cannot buy, and it is lost if nobody keeps it or reads it in the days that follow. After every incident we write down what happened, what was done and what is still open, and that document stays with you.
Backups have weight too
A full backup run against the same database adds load exactly where there is none to spare, and scheduling it at the wrong hour turns a tight day into a down day. It is taken from a replica and outside peak hours, kept inside the European Union, and test-restored every so often to know that it works.
Answering your questions
What people ask us about Support and Maintenance in Lisbon.
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