Scaling Telemedicine Platforms with Cloud-Native DevOps: An Architecture for Reliable Patient Services
DOI:
https://doi.org/10.63282/3117-5481/AIJCST-V3I2P104Keywords:
Telemedicine, Cloud-Native, Micro services, Kubernetes, DevOps, Auto scaling, Healthcare ReliabilityAbstract
Telemedicine applications depend on uninterrupted patient access, rapid feature updates, and fault-tolerant data handling across distributed environments. Traditional monolithic deployments struggle to provide elastic scalability, real-time reliability, and operational resilience during unpredictable spikes in remote healthcare demands. This paper proposes a cloud-native DevOps architecture that combines micro services, container workloads, and Kubernetes orchestration to ensure reliable telemedicine service delivery. The approach aligns infrastructure automation, continuous delivery pipelines, and auto scaling policies to support dynamic patient traffic, resilient service communication, and secure data flows across modular components. Reliability is achieved by combining horizontal scaling and service mesh routing with health-checking, rollback mechanisms, and distributed monitoring that treat patient-facing services as independently deployable units. The resulting design supports dependable consultations, responsive clinical workflows, and stable telehealth performance without interrupting active patient sessions. By embracing DevOps automation and micro service decomposition, telemedicine systems can evolve continuously while maintaining consistent service quality under demanding operational conditions
References
[1] M. S. Jalali, A. Landman, and W. J. Gordon, “Telemedicine, privacy, and information security in the age of covid-19,” Journal of the American Medical Informatics Association, vol. 28, no. 3, pp. 671–672, 2021. [Online]. Available: https://doi.org/10.1093/jamia/ocaa310
[2] V. J. Watzlaf, L. Zhou, D. R. DeAlmeida, and L. M. Hartman, “A systematic review of research studies examining telehealth privacy and security practices used by healthcare providers,” International Journal of Telerehabilitation, vol. 9, no. 2, p. 39–58, Nov. 2017. [Online]. Available: https://telerehab.hpu.edu/index.php/Telerehab/article/view/6231
[3] M. Shahin, M. A. Babar, and L. Zhu, “Continuous integration, delivery and deployment: A systematic review,” IEEE Access, vol. 5, pp. 3909– 3943, 2017. [Online]. Available: https://doi.org/10.1109/ACCESS.2017. 2685629
[4] M. M. R. Hasan, E. L. Asaf, B. Paik, and J.-F. Letarte, “Testing practices for infrastructure as code,” ACM Software Engineering Notes, vol. 45, no. 4, pp. 1–7, 2020. [Online]. Available: https: //doi.org/10.1145/3416504.3424334
[5] T. Kanwal, A. Anjum, and A. Khan, “Privacy preservation in e-health cloud: Taxonomy, privacy requirements, and feasibility analysis,” Cluster Computing, pp. 1–19, 2020. [Online]. Available: https://doi.org/10.1007/s10586-020-03106-1
[6] A. Rahman and L. Williams, “Source code properties of defective infrastructure as code scripts,” Information and Software Technology, vol. 112, pp. 148–163, 2019. [Online]. Available: https://doi.org/10. 1016/j.infsof.2019.04.013
[7] K. Kaur, S. Garg, G. Kaddoum, S. H. Ahmed, and M. Atiquzzaman, “Keids: Kubernetes-based energy and interference driven scheduler for industrial iot in edge-cloud ecosystem,” IEEE Internet of Things Journal, vol. 7, no. 5, pp. 4228–4237, 2020.
[8] I. Keshta and A. Odeh, “Security and privacy of electronic health records: Concerns and challenges,” Egyptian Informatics Journal, vol. 22, no. 2, pp. 177–183, 2021. [Online]. Available: https://doi.org/10.1016/j.eij.2020.07.003
[9] T. M. Hale and J. C. Kvedar, “Privacy and security concerns in telehealth,” AMA Journal of Ethics, vol. 16, no. 12, pp. 981–985, 2014. [Online]. Available: https://doi.org/10.1001/virtualmentor.2014. 16.12.jdsc1-1412
[10] A. Rahman, M. Rahman, and L. Williams, “The seven sins: Security smells in infrastructure as code scripts,” in Proceedings of the 41st International Conference on Software Engineering, 2019, pp. 1–12. [Online]. Available: https://doi.org/10.1109/ICSE.2019.00033
