From Heavyweights to Obscurities: A Critical Review of 13 Java Web Frameworks

Evaluation Dimensions

Performance : throughput, response time, resource usage

Ecosystem Maturity : community activity, documentation quality, third‑party library support

Learning Curve : onboarding difficulty, conceptual complexity

Development Efficiency : code volume, development speed, maintenance cost

Enterprise Adoption : market share, large‑company usage

Innovation : technical advancement, architectural ideas

Top Tier (夯)

Spring Boot

Reason : 42% usage in micro‑service surveys (Azul "State of Java 2025"), making it the dominant Java web framework.

Advantages : convention‑over‑configuration, auto‑configuration, full Spring Cloud stack, extensive documentation, easy hiring.

Applicable : enterprise applications, micro‑service architectures, any scenario requiring stability.

Objective Data : 79k+ GitHub stars; 150,650 Stack Overflow questions tagged spring-boot.

High‑Performance Tier (顶级)

Quarkus

Reason : Cloud‑native framework with dramatically faster startup and lower memory usage.

Advantages : native GraalVM support, millisecond‑level cold start, container‑friendly, development experience close to Spring Boot.

Applicable : Kubernetes, serverless, micro‑services, workloads demanding extreme performance.

Objective Data : Startup 0.049 s (Quarkus native) vs 1.909 s (Spring Boot JVM); Max RSS 70.5 MB vs 388.9 MB (≈ 82% reduction).

Micronaut

Reason : Compile‑time dependency injection eliminates reflection overhead.

Advantages : fast startup, low memory footprint, GraalVM support, friendly to reactive programming.

Applicable : micro‑services, cloud‑native applications, performance‑sensitive scenarios.

Objective Data : Startup 0.656 s (Micronaut JVM) vs 1.909 s (Spring Boot JVM) – about 2.9× faster; Max RSS 253.2 MB vs 388.9 MB (≈ 35% reduction).

Vert.x

Reason : Asynchronous, non‑blocking core excels in high‑concurrency environments.

Advantages : event‑driven, Reactor model, extreme performance, multi‑language support.

Applicable : high‑concurrency, real‑time systems, WebSocket, IoT.

Objective Data : Continuously appears in the TechEmpower Framework Benchmarks under vertx/ and vertx-web/ implementations.

Specialized Tier (人上人)

Helidon

Reason : Oracle‑backed MicroProfile implementation, lightweight micro‑service framework.

Advantages : modular design, reactive support, GraalVM native compilation, well‑structured documentation.

Applicable : micro‑services, cloud‑native applications, teams preferring standards.

Market : Less known than top‑tier frameworks but technically solid.

Javalin

Reason : Minimalist framework that works well with both Kotlin and Java.

Advantages : low learning curve, concise code, decent performance, suited for small projects.

Applicable : RESTful APIs, prototyping, teaching projects.

Positioning : Similar to Node.js Express but with a smaller ecosystem.

Dropwizard

Reason : Veteran micro‑service framework integrating Jetty, Jersey, Jackson.

Advantages : out‑of‑the‑box, ops‑friendly (built‑in metrics), stable and reliable.

Applicable : RESTful services, projects needing rapid launch.

Current Status : Once prominent, now squeezed by Spring Boot and newer frameworks.

Functional but Unremarkable (NPC)

Play Framework

Reason : Scala/Java dual‑stack with reactive architecture, but low visibility in the Java ecosystem.

Advantages : asynchronous, hot‑reload, REST‑friendly.

Disadvantages : steep learning curve, community more active in Scala, few Java users.

Positioning : Better suited for Scala developers.

Grails

Reason : Full‑stack Groovy framework, convention over configuration.

Advantages : fast development, ideal for rapid prototyping.

Disadvantages : Groovy is niche, average performance, low enterprise adoption.

Current Status : Largely replaced by Spring Boot.

Apache Wicket

Reason : Component‑based web framework with an object‑oriented mindset.

Advantages : no need for JavaScript, fits traditional Java developers.

Disadvantages : front‑back separation considered outdated, scarce learning resources.

Current Status : Maintenance mode, rarely chosen for new projects.

Legacy Tier (拉完了)

Struts 2

Reason : Former champion now obsolete.

Disadvantages : frequent security vulnerabilities, outdated architecture, stagnant community.

Current Status : Maintained only in legacy projects; prohibited for new development.

Historical Role : Part of the "SSH" trio, now phased out.

JSF (JavaServer Faces)

Reason : Part of the Java EE standard but offers poor developer experience.

Disadvantages : heavyweight, low productivity, tight front‑back coupling.

Current Status : Used mainly in legacy government or banking systems; otherwise abandoned.

Native Servlet + JSP

Reason : Raw technology stack requiring hand‑crafted code.

Disadvantages : extremely low efficiency, hard maintenance, all functionality must be written manually.

Current Status : Suitable only for teaching or interview practice.