Alternatives to Dropwizard logo

Alternatives to Dropwizard

Spring Boot, Play, Spring, Dropwizard Metrics, and Jersey are the most popular alternatives and competitors to Dropwizard.
312
182

What is Dropwizard and what are its top alternatives?

Dropwizard is a Java framework that combines various libraries to create standalone web services. It includes Jetty, Jersey, Jackson, and Metrics for building APIs quickly. Key features include easy deployment, centralized configuration, and monitoring capabilities. However, one limitation is that it may not be as flexible for complex applications compared to other frameworks.

  1. Spring Boot: Spring Boot provides a powerful platform for building Java-based web applications with minimal configuration. Key features include a wide range of out-of-the-box modules, robust dependency injection, and seamless integration with other Spring projects. Pros: extensive community support, flexible configuration options. Cons: learning curve for beginners, potential performance overhead.

  2. Micronaut: Micronaut is a modern JVM-based framework designed for building modular and lightweight microservices. Key features include fast startup time, dependency injection, and cloud-native support. Pros: efficient memory usage, integration with GraalVM for native image generation. Cons: less mature ecosystem compared to other frameworks, limited community resources.

  3. Quarkus: Quarkus is a Kubernetes-native Java framework that optimizes Java specifically for containers and serverless applications. Key features include high performance, low memory footprint, and seamless integration with popular Java libraries. Pros: rapid development cycle, support for live coding. Cons: limited support for certain Java features, potential compatibility issues with existing codebases.

  4. Helidon: Helidon is a collection of Java libraries for building microservices that are lightweight, reactive, and cloud-native. Key features include support for multiple programming models, integration with Eclipse MicroProfile, and seamless integration with Kubernetes. Pros: easy setup and deployment, built-in security features. Cons: limited tooling and documentation compared to other frameworks, smaller community.

  5. Play Framework: Play Framework is a reactive web application framework for building scalable and high-performance web applications using Java or Scala. Key features include asynchronous programming support, hot code reloading, and built-in testing tools. Pros: intuitive API design, support for reactive programming. Cons: learning curve for beginners, potential performance bottlenecks in complex applications.

  6. Vert.x: Vert.x is a lightweight and reactive toolkit for building high-performance microservices and distributed applications on the JVM. Key features include event-driven programming, fast performance, and support for multiple programming languages. Pros: non-blocking I/O model, efficient memory usage. Cons: steep learning curve for beginners, limited support for enterprise features.

  7. Spark Java: Spark Java is a micro web framework for creating web applications in Java with minimal effort. Key features include a simple and expressive API, easy routing, and template engine support. Pros: lightweight and easy to get started, seamless integration with other Java libraries. Cons: limited scalability for large and complex applications, lack of advanced features compared to other frameworks.

  8. Ratpack: Ratpack is a simple, lightweight, and asynchronous web framework for Java that focuses on high performance and developer productivity. Key features include reactive programming, simple API, and flexible configuration options. Pros: fast performance, easy-to-use DSL for defining routes. Cons: limited community support and resources, may require additional setup for complex scenarios.

  9. Jooby: Jooby is a modern and modular micro web framework for Java that simplifies web development through a powerful routing engine and easy-to-use syntax. Key features include support for dependency injection, built-in WebSocket support, and simplified configuration. Pros: flexible and modular design, integration with popular Java technologies. Cons: smaller community compared to other frameworks, potential learning curve for beginners.

  10. Ninja Framework: Ninja Framework is a full-stack web application framework for Java that focuses on simplicity, ease of use, and performance. Key features include support for RESTful APIs, seamless integration with frontend technologies, and built-in testing capabilities. Pros: intuitive design, fast performance. Cons: limited documentation and examples, lack of advanced features for complex applications.

Top Alternatives to Dropwizard

  • 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. ...

  • Play
    Play

    Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications. ...

  • 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. ...

  • Dropwizard Metrics
    Dropwizard Metrics

    It is a Java library which gives you insight into what your code does in production. It provides a powerful toolkit of ways to measure the behavior of critical components in your production environment. It provides you with full-stack visibility. ...

  • Jersey
    Jersey

    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鈥檚 own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development. ...

  • Micronaut Framework
    Micronaut Framework

    It is a modern, JVM-based, full-stack framework for building modular, easily testable microservice and serverless applications. It features a Dependency Injection and Aspect-Oriented Programming runtime that uses no reflection. ...

  • Prometheus
    Prometheus

    Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. ...

  • Quarkus
    Quarkus

    It tailors your application for GraalVM and HotSpot. Amazingly fast boot time, incredibly low RSS memory (not just heap size!) offering near instant scale up and high density memory utilization in container orchestration platforms like Kubernetes. We use a technique we call compile time boot. ...

Dropwizard alternatives & related posts

Spring Boot logo

Spring Boot

26K
23.6K
1K
Create Spring-powered, production-grade applications and services with absolute minimum fuss
26K
23.6K
+ 1
1K
PROS OF SPRING BOOT
  • 149
    Powerful and handy
  • 134
    Easy setup
  • 128
    Java
  • 90
    Spring
  • 85
    Fast
  • 46
    Extensible
  • 37
    Lots of "off the shelf" functionalities
  • 32
    Cloud Solid
  • 26
    Caches well
  • 24
    Productive
  • 24
    Many receipes around for obscure features
  • 23
    Modular
  • 23
    Integrations with most other Java frameworks
  • 22
    Spring ecosystem is great
  • 21
    Auto-configuration
  • 21
    Fast Performance With Microservices
  • 18
    Community
  • 17
    Easy setup, Community Support, Solid for ERP apps
  • 15
    One-stop shop
  • 14
    Easy to parallelize
  • 14
    Cross-platform
  • 13
    Easy setup, good for build erp systems, well documented
  • 13
    Powerful 3rd party libraries and frameworks
  • 12
    Easy setup, Git Integration
  • 5
    It's so easier to start a project on spring
  • 4
    Kotlin
  • 1
    Microservice and Reactive Programming
  • 1
    The ability to integrate with the open source ecosystem
CONS OF SPRING BOOT
  • 23
    Heavy weight
  • 18
    Annotation ceremony
  • 13
    Java
  • 11
    Many config files needed
  • 5
    Reactive
  • 4
    Excellent tools for cloud hosting, since 5.x
  • 1
    Java 馃槖馃槖

related Spring Boot posts

Praveen Mooli
Engineering Manager at Taylor and Francis | 19 upvotes 路 4M views

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

See more

Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

See more
Play logo

Play

753
606
496
The High Velocity Web Framework For Java and Scala
753
606
+ 1
496
PROS OF PLAY
  • 81
    Scala
  • 55
    Web-friendly architecture
  • 55
    Built on akka
  • 50
    Stateless
  • 47
    High-scalable
  • 46
    Fast
  • 40
    Open source
  • 34
    Java
  • 27
    High velocity
  • 24
    Fun
  • 9
    Lightweight
  • 8
    Non-blocking io
  • 6
    Developer friendly
  • 5
    Simple template engine
  • 4
    Scalability
  • 3
    Pure love
  • 2
    Resource efficient
CONS OF PLAY
  • 3
    Evolves fast, keep up with releases
  • 1
    Unnecessarily complicated

related Play posts

Alex A

Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?

See more

Scala Akka Kafka Play Spark Framework Hiring for various companies around London and Europe,

Salarys upto 拢100,000 Junior-Senior Engineers, Scala/Akka/Kafka

Get in touch with me for more details!

Jasmine.wells@signifytechnology.com

See more
Spring logo

Spring

4K
4.8K
1.1K
Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
4K
4.8K
+ 1
1.1K
PROS OF SPRING
  • 230
    Java
  • 157
    Open source
  • 136
    Great community
  • 123
    Very powerful
  • 114
    Enterprise
  • 64
    Lot of great subprojects
  • 60
    Easy setup
  • 44
    Convention , configuration, done
  • 40
    Standard
  • 31
    Love the logic
  • 13
    Good documentation
  • 11
    Dependency injection
  • 11
    Stability
  • 9
    MVC
  • 6
    Easy
  • 3
    Makes the hard stuff fun & the easy stuff automatic
  • 3
    Strong typing
  • 2
    Code maintenance
  • 2
    Best practices
  • 2
    Maven
  • 2
    Great Desgin
  • 2
    Easy Integration with Spring Security
  • 2
    Integrations with most other Java frameworks
  • 1
    Java has more support and more libraries
  • 1
    Supports vast databases
  • 1
    Large ecosystem with seamless integration
  • 1
    OracleDb integration
  • 1
    Live project
CONS OF SPRING
  • 15
    Draws you into its own ecosystem and bloat
  • 3
    Verbose configuration
  • 3
    Poor documentation
  • 3
    Java
  • 2
    Java is more verbose language in compare to python

related Spring posts

Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

See more

I am consulting for a company that wants to move its current CubeCart e-commerce site to another PHP based platform like PrestaShop or Magento. I was interested in alternatives that utilize Node.js as the primary platform. I currently don't know PHP, but I have done full stack dev with Java, Spring, Thymeleaf, etc.. I am just unsure that learning a set of technologies not commonly used makes sense. For example, in PrestaShop, I would need to work with JavaScript better and learn PHP, Twig, and Bootstrap. It seems more cumbersome than a Node JS system, where the language syntax stays the same for the full stack. I am looking for thoughts and advice on the relevance of PHP skillset into the future AND whether the Node based e-commerce open source options can compete with Magento or Prestashop.

See more
Dropwizard Metrics logo

Dropwizard Metrics

25
18
0
Capturing JVM- and application-level metrics
25
18
+ 1
0
PROS OF DROPWIZARD METRICS
    Be the first to leave a pro
    CONS OF DROPWIZARD METRICS
      Be the first to leave a con

      related Dropwizard Metrics posts

      Jersey logo

      Jersey

      151
      125
      6
      A REST framework that provides a JAX-RS implementation
      151
      125
      + 1
      6
      PROS OF JERSEY
      • 4
        Lightweight
      • 1
        Fast Performance With Microservices
      • 1
        Java standard
      CONS OF JERSEY
        Be the first to leave a con

        related Jersey posts

        Micronaut Framework logo

        Micronaut Framework

        184
        328
        52
        A JVM-based full-stack framework
        184
        328
        + 1
        52
        PROS OF MICRONAUT FRAMEWORK
        • 12
          Compilable to machine code
        • 8
          Tiny memory footprint
        • 7
          Open source
        • 7
          Almost instantaneous startup
        • 6
          Tiny compiled code size
        • 4
          High Escalability
        • 2
          Minimal overhead
        • 2
          Hasn't Servlet API
        • 2
          Simplified reactive programming
        • 1
          Serverless support
        • 1
          Jakarta EE
        CONS OF MICRONAUT FRAMEWORK
        • 3
          No hot reload

        related Micronaut Framework posts

        Prometheus logo

        Prometheus

        4.3K
        3.8K
        239
        An open-source service monitoring system and time series database, developed by SoundCloud
        4.3K
        3.8K
        + 1
        239
        PROS OF PROMETHEUS
        • 47
          Powerful easy to use monitoring
        • 38
          Flexible query language
        • 32
          Dimensional data model
        • 27
          Alerts
        • 23
          Active and responsive community
        • 22
          Extensive integrations
        • 19
          Easy to setup
        • 12
          Beautiful Model and Query language
        • 7
          Easy to extend
        • 6
          Nice
        • 3
          Written in Go
        • 2
          Good for experimentation
        • 1
          Easy for monitoring
        CONS OF PROMETHEUS
        • 12
          Just for metrics
        • 6
          Bad UI
        • 6
          Needs monitoring to access metrics endpoints
        • 4
          Not easy to configure and use
        • 3
          Supports only active agents
        • 2
          Written in Go
        • 2
          TLS is quite difficult to understand
        • 2
          Requires multiple applications and tools
        • 1
          Single point of failure

        related Prometheus posts

        Matt Menzenski
        Senior Software Engineering Manager at PayIt | 16 upvotes 路 1M views

        Grafana and Prometheus together, running on Kubernetes , is a powerful combination. These tools are cloud-native and offer a large community and easy integrations. At PayIt we're using exporting Java application metrics using a Dropwizard metrics exporter, and our Node.js services now use the prom-client npm library to serve metrics.

        See more
        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber | 15 upvotes 路 5M views

        Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

        By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node鈥檚 disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

        To ensure the scalability of Uber鈥檚 metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

        https://eng.uber.com/m3/

        (GitHub : https://github.com/m3db/m3)

        See more
        Quarkus logo

        Quarkus

        307
        379
        79
        A Kubernetes Native Java stack tailored for OpenJDK HotSpot and GraalVM, crafted from the best of breed Java...
        307
        379
        + 1
        79
        PROS OF QUARKUS
        • 13
          Fast startup
        • 13
          Open source
        • 11
          Low memory footprint
        • 10
          Integrated with GraalVM
        • 10
          Produce native code
        • 9
          Hot Reload
        • 7
          AOT compilation
        • 6
          Reactive
        CONS OF QUARKUS
        • 2
          Boilerplate code when using Reflection

        related Quarkus posts

        Shared insights
        on
        JavaJavaQuarkusQuarkusAWS LambdaAWS Lambda

        We are working on a transaction processing application and everything needs to happen in real-time. I have used AWS Lambda with Quarkus + Java, and struggled with cold start time however Lambda is still cost effective. so wanted to understand which one will be suitable as alternative to lambda services.

        See more
        Joshua Dean K眉pper
        CEO at Scrayos UG (haftungsbeschr盲nkt) | 4 upvotes 路 259.6K views

        We use Quarkus with native compilation in GraalVM for our global REST-API "Charon", that can be used by every developer to request user, server and game-data (protected through OAuth2). Quarkus offers a reliable framework, library and stack for high-quality APIs and integrates Vert.x into its core.

        GraalVM pushes the performance boundaries even further with the ability to perform ahead-of-time native compilation so we can reach an incredible small memory-footprint and fast bootup-times that we need for our microservices architecture.

        See more