<![CDATA[Universitas Terbuka (UT), Indonesia's distance-learning university with 39 regional offices, previously ran database backups separately at each office, leaving the central office without visibility into backup status, history, or success rates. Running large backups synchronously inside the main application also posed a potential risk to service performance. This study develops an asynchronous database backup architecture and a centralized monitoring dashboard for SIBU (Sistem Informasi Backup Universitas Terbuka), using a task queue to separate backup execution from the main application. The system was built with the waterfall method (requirement, design, implementation, and testing). RabbitMQ acts as the message broker in a competing consumer pattern: the backend publishes backup jobs to a queue, and a couple independent workers consume them, dumps the database, encrypts the output, and streams it to MinIO object storage. Black-box testing showed that all tested scenarios, including job submission, queueing, status updates, failure handling, and the central reporting dashboard, produced the expected results. The architecture is designed to keep backup workloads outside the main API process and to give the central office a single view of backup status across regional offices. Effects on latency, throughput, and resource usage were not measured and are left for future load testing.]]>
Copyrights © 2026
