Dropwizard vs Spring Boot: What are the differences?
Dropwizard: Java framework for developing ops-friendly, high-performance, RESTful web services. 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; Spring Boot: Create Spring-powered, production-grade applications and services with absolute minimum fuss. 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.
Dropwizard and Spring Boot can be primarily classified as "Frameworks (Full Stack)" tools.
"Quick and easy to get a new http service going" is the primary reason why developers consider Dropwizard over the competitors, whereas "Powerful and handy" was stated as the key factor in picking Spring Boot.
Dropwizard and Spring Boot are both open source tools. It seems that Spring Boot with 39.8K GitHub stars and 25.8K forks on GitHub has more adoption than Dropwizard with 7.25K GitHub stars and 3.04K GitHub forks.
MIT, Intuit, and PedidosYa are some of the popular companies that use Spring Boot, whereas Dropwizard is used by Yammer, Opower, and ClassPass. Spring Boot has a broader approval, being mentioned in 333 company stacks & 615 developers stacks; compared to Dropwizard, which is listed in 51 company stacks and 12 developer stacks.
What is Dropwizard?
What is Spring Boot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I use Spring-Boot because it almost let you get things done quickly for a JVM-target project, with auto configuration components and dependency management starters. It is almost perfectly tailored for microservices applications development with a single unit deployment artifact (JAR) along with support for Service Registry and Discovery, Circuit Breaker pattern...
Any third-party library or any back-end service would perfectly integrate well since Spring offers integration support for most of mainstream services, let it be a RDBMS service, a NoSQL database, a Message Broker...
Coming to day-to-day development, Spring-Boot enjoys a great community so you can get support, direction, focused guidance from almost everywhere.
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
spring boot allow my team to start building web services quickly and package it in a stand alone application
Spring-Boot allows us to create stand-alone web servers and helps us configure many of our dependencies with sane default, while maintaining flexibility where we need it.