Comparison of Java Microservice Frameworks and a Free Programmer Book Giveaway

The article begins with a promotional notice: by accessing the backend menu "学习资料—书籍" and replying with the keyword "5000", users can receive a free set of programmer books titled "程序员书籍资料一份".

Spring Cloud (Java microservice framework No.1) is highlighted as a mature, easy‑to‑use solution backed by Spring, but it requires substantial resources: at least one service‑discovery server, a possible gateway, a configuration center, service tracing, cluster monitoring, and multiple servers for scaling. Performance testing shows a pre‑test memory usage of 304 MB, which spikes to 1.5 GB during a 30‑second load test with CPU usage reaching 321 %. Startup time is about 10 seconds (JVM running for 10.915 s).

Vert.x is presented as a lightweight alternative. A single Vert.x service packs into a ~7 MB JAR and runs without an external container. Before testing, memory usage is around 65 MB; during the test it rises to 139 MB with CPU at 2.1 %. Startup time is under 1 second (0.274 s). The framework consumes very few resources, making it suitable for 1‑core, 2 GB servers, and it supports multiple languages. An open‑source gateway (VX‑API‑Gateway) is mentioned.

Other Java microservice frameworks are briefly compared:

SparkJava : small JAR (~10 MB), low memory (30‑60 MB), performance comparable to Spring Boot.

Micronaut : supports Java, Groovy, Kotlin; comprehensive microservice features; higher performance; multi‑language support; built‑in cloud‑native capabilities; recently released 1.0.0.

Javalin : extremely easy to start; flexible (sync/async); tiny JAR (4‑5 MB); about 2000 lines of source code; supports multiple languages; embeds Jetty server.

Quarkus : fast startup; small JAR (~10 MB); documentation is limited.

The article concludes that Spring Boot applications typically require at least 1 GB of memory, while Spring Cloud adds additional overhead. Vert.x offers a much lighter footprint, and the other frameworks provide various trade‑offs between size, performance, and feature set.