We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Mathematics/Comparative performance analysis of Spring Boot and Quarkus frameworks in Java applications
PeriodicalsMathematics

Comparative performance analysis of Spring Boot and Quarkus frameworks in Java applications

Checking your access to this record.

Abstract & Overview

The paper presents comparative performance characterization of two Java application development frameworks, Spring Boot and Quarkus. A representative reference application was implemented using both frameworks to enable such a comparison. The study entailed measurements in terms of multiple metrics, including compilation time, initialization time for an application, final file sizes, CPU and RAM consumption, latency in HTTP response, throughput, and efficiency of database queries. Tests were run on both JAR and native image versions with varying loads. Results convincingly showed the benefits of native Quarkus in startup performance and resource utilization. Spring Boot is still a proven option with a broader tooling universe supporting it, though. This research gives interesting input to decide on the best technology for modern Java applications.

Cite this record

Grzegorz Szymanek, Jakub Smółka (2025). Comparative performance analysis of Spring Boot and Quarkus frameworks in Java applications. Journal of Computer Sciences Institute, 37, 484–491. https://doi.org/10.35784/jcsi.8047

Copy in another style

Szymanek, G., & Smółka, J. (2025). Comparative performance analysis of Spring Boot and Quarkus frameworks in Java applications. Journal of Computer Sciences Institute, 37, 484–491. https://doi.org/10.35784/jcsi.8047
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.