StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Microframeworks
  4. Microframeworks
  5. Dropwizard vs Jersey

Dropwizard vs Jersey

OverviewComparisonAlternatives

Overview

Jersey
Jersey
Stacks217
Followers125
Votes6
Dropwizard
Dropwizard
Stacks309
Followers366
Votes182
GitHub Stars8.6K
Forks3.4K

Dropwizard vs Jersey: What are the differences?

Introduction:

This article will highlight the key differences between Dropwizard and Jersey, two popular frameworks used for building web applications. Dropwizard is a Java-based framework that combines multiple libraries, including Jersey, to simplify the development of RESTful web services. Jersey, on the other hand, is a full-featured, open-source framework specifically designed for building RESTful Web Services in Java.

  1. Dropwizard architecture: Dropwizard follows a holistic approach to building web applications. It combines several pre-existing libraries, such as Jersey for RESTful web services, Jetty for HTTP server capabilities, Jackson for JSON processing, and more. Dropwizard provides a comprehensive and integrated development stack, making it easier for developers to work on various aspects of a web application simultaneously.

  2. Jersey as a standalone framework: Jersey, as its name suggests, is primarily focused on providing a robust framework for developing RESTful web services. Unlike Dropwizard, it does not include additional libraries for aspects like web server or database connectivity out-of-the-box. Jersey can be used as a standalone framework, allowing developers the flexibility to choose the supporting libraries according to their requirements and preferences.

  3. Configuration management: Dropwizard provides built-in configuration management capabilities, allowing developers to externalize configuration settings from the application code. Dropwizard uses YAML files for configuration, making it easy to change settings without modifying the code. This separation of configuration from code promotes better maintainability and allows for easier deployment across different environments.

  4. Limited customization in Dropwizard: While Dropwizard provides a comprehensive development stack, it comes with limited customization options. Dropwizard follows a convention-over-configuration approach, making some decisions for the developers to streamline the development process. However, this can be limiting for projects requiring extensive customization or unique architectural choices.

  5. Extensive customization in Jersey: Jersey, being a standalone framework, offers developers more flexibility and control over the customizations of their web services. Developers can choose the specific libraries and configurations they want to use with Jersey, allowing for a more tailored approach to building RESTful web services. This increased flexibility can be beneficial for projects with specific requirements or complex architectures.

  6. Ease of getting started: Dropwizard provides a comprehensive, opinionated setup for building web applications, making it easier for developers to get started quickly. It simplifies the initial project setup by providing sensible defaults and integrates the required libraries seamlessly. In contrast, Jersey, being a standalone framework, requires developers to make choices and set up the necessary components manually. This may require additional effort and time to get started with a basic web application.

In summary, Dropwizard is an opinionated framework that combines multiple libraries to simplify the development of web applications, while Jersey is a standalone framework designed specifically for building RESTful web services. Dropwizard provides a holistic approach and built-in configuration management, but with limited customization options. Jersey offers extensive customization and flexibility, but requires more manual setup and decision-making.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Jersey
Jersey
Dropwizard
Dropwizard

It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.

Dropwizard is a sneaky way of making fast Java web applications. Dropwizard pulls together stable, mature libraries from the Java ecosystem into a simple, light-weight package that lets you focus on getting things done.

Track the JAX-RS API and provide regular releases of production quality Reference Implementations that ships with GlassFish; Provide APIs to extend Jersey & Build a community of users and developers; Make it easy to build RESTful Web services utilizing Java and the Java Virtual Machine.
-
Statistics
GitHub Stars
-
GitHub Stars
8.6K
GitHub Forks
-
GitHub Forks
3.4K
Stacks
217
Stacks
309
Followers
125
Followers
366
Votes
6
Votes
182
Pros & Cons
Pros
  • 4
    Lightweight
  • 1
    Java standard
  • 1
    Fast Performance With Microservices
Pros
  • 27
    Quick and easy to get a new http service going
  • 23
    Health monitoring
  • 20
    Easy setup
  • 20
    Metrics integration
  • 18
    Good conventions
Cons
  • 2
    Slightly more confusing dependencies
  • 1
    Not on ThoughtWorks radar since 2014
Integrations
Oracle
Oracle
Java
Java
Apache Maven
Apache Maven
Java EE
Java EE
Eclipse
Eclipse
Java
Java

What are some alternatives to Jersey, Dropwizard?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

ExpressJS

ExpressJS

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

Symfony

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase