National Scale With Demand Concentrated During Library Hours
The platform supports services used by public libraries across Iran, including membership, book lending, and resource discovery.
Its workload is not distributed evenly throughout the day. The highest demand is concentrated between 08:00 and 17:00, when libraries are open and most active. The environment must therefore handle a substantial share of daily requests inside a compressed window rather than relying on traffic being spread evenly over 24 hours.
The scale of the databases, the nationwide footprint of the services, and coordination across several application vendors added further operational complexity.
The Challenge: Moving Beyond Unstable, Difficult-to-Scale Infrastructure
Before the engagement, the existing environment faced limitations in server operations, load distribution, and scalability. The absence of unified operational visibility also made it harder to identify incidents early and make capacity decisions from reliable data.
The objective was not simply to move servers. The platform needed a new operating foundation: an architecture that could distribute demand, protect large databases, surface failures quickly, and give an accountable operations team the ability to respond before a local issue became a nationwide disruption.
Re-engineering and a Controlled Multi-terabyte Migration
Dropp Tempo designed and built the new cloud environment from the ground up. The resulting infrastructure spans approximately 20 cloud servers with more than 250 CPU cores and 900 GB of RAM, providing the capacity required by multiple services and concentrated daytime traffic.
The multi-terabyte data migration was planned in stages. The final service transition took place during a controlled window of approximately six hours, from 18:00 to midnight, minimizing impact on active library hours.
The target architecture distributes traffic across service nodes and uses database replication to reduce dependence on any single database instance.
From Architecture and Hardening to 24/7 Operations
Dropp Tempo's scope covers infrastructure architecture, server operations and patching, hardening, load balancing, database replication, monitoring, alerting, centralized logging, network security, and access control.
Prometheus and Grafana provide monitoring and alerting, the ELK Stack centralizes logs, and k6 supports load and capacity testing. At the network layer, pfSense, MikroTik, and controlled VPN paths govern access and traffic flows.
24/7 support, incident response, and continuous infrastructure improvement remain part of the ongoing engagement after migration.
Observability That Turns Capacity Pressure Into Action
At this scale, server availability alone does not prove service health. Dropp Tempo implemented a unified observability layer covering infrastructure resources, application services, traffic behavior, and databases.
Centralized metrics, alerts, and logs allow the operations team to recognize abnormal load earlier, isolate causes faster, and act before degradation spreads across the platform.
During one sudden traffic increase, the team detected the capacity pressure, brought additional service nodes online, and redistributed traffic across them. This rapid intervention expanded serving capacity and maintained service continuity during peak demand.
Layered Security and Data Protection
Administrative access is routed through controlled VPN paths, outbound traffic passes through a pfSense-based gateway, and server hardening and access reviews are part of ongoing operations.
Data protection combines database replication with a multi-layer backup plan. Incremental backups run every night, full database dumps are created weekly, and backup copies are retained in object storage outside the operational servers. Together, these controls reduce dependence on any single system and strengthen recovery readiness.
Measured Outcomes in Live Operation
In a measured 30-day period, the infrastructure processed more than 152 million requests at the CDN layer, transferred more than 2.5 TB of traffic, served more than 660,000 users recorded at that layer, and achieved 99.95% availability.
The incident response SLA is under 15 minutes, while the operations team continuously evaluates capacity against real usage patterns.
The outcome is more than a successful migration. The Foundation now operates on an observable, protected, and continuously managed cloud platform with the capacity and operational ownership required for nationwide services.
Retain: Responsibility Continues After Migration
Dropp Tempo's role did not end at cutover. The team continues to manage daily operations, monitor capacity, respond to incidents, maintain security and backups, and improve the platform according to real usage patterns.
This project demonstrates that national-scale reliability is not created by infrastructure capacity alone. Architecture, observability, data protection, and an experienced team accountable around the clock are what turn raw compute into a dependable public service platform.
If your organization operates a high-traffic or business-critical platform, Dropp Tempo can support the full journey—from infrastructure assessment and migration to 24/7 managed operations.