Performance Analysis of Web Microservices with Technological Convergence between REST and GraphQL API Architectures

Authors

  • Carlos Arturo Aguilar-Díaz Tecnológico Nacional de México - Instituto Tecnológico de Ciudad Madero https://orcid.org/0009-0004-2673-8211
  • Nelson Rangel-Valdez Tecnológico Nacional de México – Instituto Tecnológico de Ciudad Madero https://orcid.org/0000-0002-4745-2325
  • María Lucila Morales-Rodríguez https://orcid.org/0000-0001-5838-7445
  • Guadalupe Castilla-Valdez Tecnológico Nacional de México – Instituto Tecnológico de Ciudad Madero
  • Claudia Guadalupe Gómez-Santillán Tecnológico Nacional de México – Instituto Tecnológico de Ciudad Madero
  • Ana Lidia Martínez-Salazar Tecnológico Nacional de México – Instituto Tecnológico de Ciudad Madero
  • Pedro Martín García-Vite Tecnológico Nacional de México – Instituto Tecnológico de Ciudad Madero https://orcid.org/0000-0001-6019-7958

DOI:

https://doi.org/10.61467/2007.1558.2026.v17i5.1412

Keywords:

web microservices, REST API, GraphQL API, Software Performance, microservicios web, rendimiento del software

Abstract

Efficient data exchange between heterogeneous systems is a critical need in modern software development. REST API and GraphQL API are the dominant paradigms for web microservices implementation; however, the scientific community has not reached a consensus on which offers better performance. Both technologies offer complementary strengths worth of studying, while REST has better response time and throughput, GraphQL improves on resource consumption. This paper presents a controlled and reproducible experiment that evaluates server response time when combining both technologies in different proportions within the development of a system. Microservices were designed by combining REST and GraphQL technologies on a basic generic user management case study; a set of 32 microservices web designs, each composed by five CRUD operations and operating with server request volumes ranging from 1 to 10, accumulating up to 76,800 requests. Findings show that a web service design involving the management of 4 CRUD operations by REST and 1 by GraphQL achieves comparable or superior median response times in contrast with a design that implements all operations using REST. Particularly, when one of the read or create CRUD operations is implemented using GraphQL and the remaining with REST the response time is minimized. In the other hand, implementing one of the update or delete CRUD operations with GraphQL causes a significative worst performance. These results provide empirical evidence of the requirements that a web microservices must meet to improve its design from the combination of REST and GraphQL technologies. Hence, strategic integration of GraphQL and REST in web microservice design might result in overall performance improvements, opposing the common sense that dictates using REST will always results in the best response times.

 

Spanish-language metadata / Metadatos en español
Título en español:
Análisis del rendimiento de microservicios web con convergencia tecnológica entre arquitecturas API REST y GraphQL

Resumen:
El intercambio eficiente de datos entre sistemas heterogéneos constituye una necesidad crítica en el desarrollo moderno de software. Las API REST y GraphQL representan dos de los paradigmas predominantes para la implementación de microservicios web; sin embargo, la comunidad científica aún no ha alcanzado un consenso respecto a cuál de ellos ofrece un mejor rendimiento. Ambas tecnologías presentan fortalezas complementarias que justifican su estudio: mientras que REST ofrece mejores tiempos de respuesta y mayor rendimiento (throughput), GraphQL mejora el consumo de recursos.

Este artículo presenta un experimento controlado y reproducible que evalúa el tiempo de respuesta del servidor al combinar ambas tecnologías en diferentes proporciones durante el desarrollo de un sistema. Los microservicios se diseñaron mediante distintas combinaciones de tecnologías REST y GraphQL sobre un caso de estudio genérico y básico de gestión de usuarios. Se evaluó un conjunto de 32 diseños de microservicios web, cada uno compuesto por cinco operaciones CRUD y sometido a volúmenes de solicitudes al servidor comprendidos entre 1 y 10, hasta acumular un total de 76.800 solicitudes.

Los resultados muestran que un diseño de servicio web en el que cuatro operaciones CRUD son gestionadas mediante REST y una mediante GraphQL alcanza tiempos medianos de respuesta comparables o superiores a los de un diseño que implementa todas las operaciones mediante REST. En particular, cuando una de las operaciones CRUD de lectura o creación se implementa mediante GraphQL y las restantes mediante REST, el tiempo de respuesta se minimiza.

Por el contrario, implementar mediante GraphQL una de las operaciones CRUD de actualización o eliminación produce un deterioro significativo del rendimiento. Estos resultados aportan evidencia empírica sobre los requisitos que deben cumplir los microservicios web para mejorar su diseño mediante la combinación de tecnologías REST y GraphQL.

En consecuencia, una integración estratégica de GraphQL y REST en el diseño de microservicios web podría producir mejoras globales en el rendimiento, en contraste con la idea generalizada de que el uso exclusivo de REST siempre proporciona los mejores tiempos de respuesta.

Palabras Claves:
microservicios web, API REST, API GraphQL, rendimiento del software

Smart citations:

SciteAI
Dimensions.
Open Alex.

References

Ala-Laurinaho, R., Mattila, J., Autiosalo, J., Hietala, J., Laaki, H., & Tammi, K. (2022). Comparison of REST and GraphQL interfaces for OPC UA. Computers, 11(5), Article 65. https://doi.org/10.3390/computers11050065

Amazon Web Services. (n.d.). Microservices. Retrieved May 25, 2026, from https://aws.amazon.com/microservices/

Amazon Web Services. (n.d.). What is an API (application programming interface)? Retrieved May 25, 2026, from https://aws.amazon.com/what-is/api/

Bogutskii, V. (2025). Features of REST API development for high-load systems. International Journal of Scientific Engineering and Science, 9(3), 67–71. Journal PDF

Brito, G., Mombach, T., & Valente, M. T. (2019). Migrating to GraphQL: A practical assessment. In 2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER) (pp. 140–150). IEEE. https://doi.org/10.1109/SANER.2019.8667986

Brito, G., & Valente, M. T. (2020). REST vs GraphQL: A controlled experiment. In 2020 IEEE International Conference on Software Architecture (ICSA) (pp. 81–91). IEEE. https://doi.org/10.1109/ICSA47634.2020.00016

Devalla, S. (2024). Enterprise-scale evaluation of REST and GraphQL: Balancing performance, scalability, and resource utilization. International Journal of Core Engineering & Management, 7(12), 396–416. Official journal copy

Elghazal, M. S. M., Aneiba, A., & Shahra, E. Q. (2025). Performance evaluation of REST and GraphQL API models in microservices software development domain. In Proceedings of the 21st International Conference on Web Information Systems and Technologies: Volume 1—WEBIST (pp. 83–91). SciTePress. https://doi.org/10.5220/0013729900003985

China, C. R. (2024, March 29). GraphQL vs. REST API: What’s the difference? IBM. IBM article

Jin, R., Cordingly, R., Zhao, D., & Lloyd, W. (2025). GraphQL vs. REST: Investigating performance and scalability for serverless data persistence. In 2025 IEEE International Conference on Cloud Engineering (IC2E) (pp. 155–161). IEEE. https://doi.org/10.1109/IC2E65552.2025.00031

Khan, I. A., Mishra, H., & Choubey, K. (2025). A comparative analysis of REST and GraphQL APIs: Performance, efficiency, and developer experience. International Journal of Advanced Multidisciplinary Scientific Research, 8(4), 29–39. https://doi.org/10.31426/ijamsr.2025.8.4.8212

Kurniawati, D., Kusjani, A., Buwono, R. C., & Ridhoni, M. A. (2025). Pengembangan sistem transformasi dan konversi data berbasis web menggunakan arsitektur RESTful API. Bulletin of Computer Science Research, 5(6), 1395–1402. https://doi.org/10.47065/bulletincsr.v5i6.818

Lawi, A., Panggabean, B. L. E., & Yoshida, T. (2021). Evaluating GraphQL and REST API services performance in a massive and intensive accessible information system. Computers, 10(11), Article 138. https://doi.org/10.3390/computers10110138

Montgomery, D. C., & Runger, G. C. (2013). Applied statistics and probability for engineers (6th ed.). Wiley.

Quiña-Mera, A., Fernandez, P., García, J. M., & Ruiz-Cortés, A. (2023). GraphQL: A systematic mapping study. ACM Computing Surveys, 55(10), Article 202. https://doi.org/10.1145/3561818

Sayago Heredia, J., Flores-García, E., & Solano, A. R. (2020). Comparative analysis between standards oriented to web services: SOAP, REST and GRAPHQL. In M. Botto-Tobar, M. Zambrano Vizuete, P. Torres-Carrión, S. Montes León, G. Pizarro Vásquez, & B. Durakovic (Eds.), Applied technologies (pp. 286–300). Springer. https://doi.org/10.1007/978-3-030-42517-3_22

Soni, A., & Ranga, V. (2019). API features individualizing of web services: REST and SOAP. International Journal of Innovative Technology and Exploring Engineering, 8(9S), 664–671. https://doi.org/10.35940/ijitee.I1107.0789S19

Vadlamani, S. L., Emdon, B., Arts, J., & Baysal, O. (2021). Can GraphQL replace REST? A study of their efficiency and viability. In 2021 IEEE/ACM 8th International Workshop on Software Engineering Research and Industrial Practice (SER&IP) (pp. 10–17). IEEE. https://doi.org/10.1109/SER-IP52554.2021.00009

Wittern, E., Cha, A., & Laredo, J. A. (2018). Generating GraphQL-wrappers for REST(-like) APIs. In T. Mikkonen, R. Klamma, & J. Hernández (Eds.), Web engineering (pp. 65–83). Springer. https://doi.org/10.1007/978-3-319-91662-0_5

Downloads

Published

2026-09-06

How to Cite

Aguilar-Díaz, C. A., Rangel-Valdez, N., Morales-Rodríguez, M. L., Castilla-Valdez, G., Gómez-Santillán, C. G., Martínez-Salazar, A. L., & García-Vite, P. M. (2026). Performance Analysis of Web Microservices with Technological Convergence between REST and GraphQL API Architectures. International Journal of Combinatorial Optimization Problems and Informatics, 17(5), 195–211. https://doi.org/10.61467/2007.1558.2026.v17i5.1412

Issue

Section

Articles

Most read articles by the same author(s)

<< < 1 2