Operations case study · Customer name withheld
Keep publishing while the platform evolves.
For websites that publish new content every day, maintenance and improvement have to move together. The work depends on understanding the servers, the application and the people using it.
Behind websites that need to run every day.
Care for the platform people use, the data it depends on and the servers beneath it.
Web platform
Maintain customized PHP and WordPress while considering how the content team works.
Databases
Support the data layer and read-workload separation used across multiple websites.
Servers
Maintain Linux and infrastructure alongside improvements in the relevant project stages.
Monitoring and backup
Use monitoring and logs to investigate issues while maintaining backup systems.
The work behind the websites
The customer operates multiple content websites with different needs and periods of higher traffic. The platform uses PHP and customized WordPress, so support has to extend beyond the application to databases, logs and backups.
UNIXDEV takes care of infrastructure alongside platform maintenance. Improvements and migration work therefore have to account for the services the customer still uses every day.
What the team looks after
Servers and databases
Linux infrastructure and the database layer, including separating read workloads to support the group of websites.
The existing web platform
Customized PHP and WordPress applications, with version and infrastructure improvements in the relevant project stages.
Monitoring and investigation
Monitoring and logs that help the team investigate when a system behaves unexpectedly.
Backups
Backup systems maintained alongside the infrastructure serving the live websites.
What the continuing engagement shows
Daily operations
Keep it running
The servers, databases and platform the customer uses to do their work.
System improvements
Make needed changes
Repairs and technology changes delivered in the relevant project stages.
Continuity
Make it supportable
The scope, responsibilities and information a team needs to take over.
The work continues across successive contract periods, covering both the existing platform and improvements. The team works with the constraints of the current system as new requirements arise.
Changes in system ownership and technology happen at different stages. Cloud migration and version upgrades are separate workstreams; this case should not be read as a claim that every part was completed at the same time.
This account is based on recorded scope and maintenance history. It excludes customer names, contract details and identifying architecture. It does not establish an uptime figure or predict the result of another project.
Preparing to change your support team?
These three areas help a new team understand the work before taking responsibility.
Critical work
What must keep running?
Identify essential sites and workflows, peak periods and the impact of an outage.
Access and responsibilities
Who owns each part?
Identify owners of code, hosting and databases, and the access that needs to be transferred.
A way to recover
What is still untested?
Check restore procedures, deployment steps and the conditions for rolling back a change.
You can start with the information you have. Keep assessment work separate from repairs so everyone understands what has been checked and what is still unknown.