Your application has gone into production. Who is taking care of it now?
O deploy terminou, o domínio está funcionando e os primeiros usuários começaram a acessar. Parece que o projeto está concluído. Mas algumas perguntas continuam abertas: quem acompanha os erros? Quem atualiza o ambiente? Quem verifica os backups? E quem assume quando o sistema fica indisponível? Essas responsabilidades precisam ser combinadas entre quem desenvolve, quem contrata e quem fornece a…
An article discusses the often-overlooked responsibilities that come after a software project is completed and deployed. These responsibilities include monitoring errors, updating the environment, verifying backups, and handling system downtime. To organize these tasks, a roadmap is suggested that involves separating application and infrastructure responsibilities, defining alert procedures, planning data recovery, organizing access, and preparing for rollbacks before updates.
A checklist is also provided to ensure that all necessary steps are taken before publishing changes, including designating responsible individuals, documenting responsibilities, and establishing procedures for recovery and validation. The AzureWeb site is mentioned as an example.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.