Eclipse Jetty
Java web frameworks
Web frameworks
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if Eclipse Jetty and its alternatives fit your requirements.
Completely free
Free Trial unavailable
Free version
Small
Medium
Large
- Information technology and software
- Education and training
- Media and communications
What is Eclipse Jetty
Eclipse Jetty is a Java-based HTTP server and Servlet container used to run web applications and APIs. It is commonly embedded into Java applications or used as a standalone server for deploying Servlet/Jakarta EE web components. Jetty focuses on a small footprint, embeddability, and support for modern web protocols alongside the Java Servlet specification. It is typically used by Java developers building services that need an in-process web server rather than a full application server.
Embeddable server architecture
Jetty is designed to be embedded directly into Java applications, which supports self-contained deployments and programmatic server configuration. This model fits microservice-style services and developer-controlled runtime packaging. It reduces reliance on external application server administration for many use cases. Teams can ship a single JVM process that includes the web runtime.
Standards-based Servlet support
Jetty implements the Java Servlet specification (and related Jakarta EE web components depending on version), enabling portability for many web applications. This helps teams run standard Servlet-based frameworks and libraries without rewriting to a proprietary API. It also supports common deployment patterns such as WAR files in addition to embedded setups. Standards alignment can simplify integration with existing Java web stacks.
Protocol and async capabilities
Jetty includes support for modern HTTP features and asynchronous request handling, which is important for high-concurrency services. Its architecture supports non-blocking I/O patterns used by many Java web workloads. This can improve resource utilization compared with purely thread-per-request designs in some scenarios. It is often selected when teams need fine-grained control over HTTP behavior.
Not a full web framework
Jetty provides the server/container layer, not an end-to-end application framework with built-in dependency injection, ORM, or scaffolding. Teams typically pair it with additional libraries to cover routing, application structure, data access, and security. This increases solution design work compared with integrated frameworks. It can also lead to more variation across projects if standards are not enforced.
Configuration can be low-level
Many Jetty capabilities are exposed through programmatic APIs and server configuration concepts that require HTTP and container knowledge. Compared with higher-level frameworks, developers may spend more time on wiring, tuning, and operational settings. Misconfiguration can affect security headers, TLS settings, or request handling behavior. Organizations may need experienced Java platform engineers to standardize configurations.
Jakarta transition complexity
Ecosystem changes from javax.* to jakarta.* namespaces can affect compatibility across Jetty versions and dependent libraries. Upgrades may require coordinated changes to application dependencies and build configurations. This can be challenging for legacy Servlet applications or mixed dependency trees. Teams should validate target Jetty and Servlet/Jakarta versions early in modernization projects.
Plan & Pricing
| Plan | Price | Key features & notes |
|---|---|---|
| Open-source (Eclipse Jetty) | $0 — Free | Distributed under the Eclipse Public License 2.0 and Apache License 2.0; downloadable from the official Jetty site; community-supported. |
Seller details
Eclipse Foundation AISBL
Brussels, Belgium
2004
Non-profit
https://www.eclipse.org/
https://x.com/EclipseFdn
https://www.linkedin.com/company/eclipse-foundation/
