Alternatives to Dropwizard logo

Alternatives to Dropwizard

Spring Boot, Play, Spring, Dropwizard Metrics, and Node.js are the most popular alternatives and competitors to Dropwizard.
208
170
+ 1
162

What is Dropwizard and what are its top alternatives?

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.
Dropwizard is a tool in the Frameworks (Full Stack) category of a tech stack.
Dropwizard is an open source tool with 7.6K GitHub stars and 3.1K GitHub forks. Here’s a link to Dropwizard's open source repository on GitHub

Dropwizard alternatives & related posts

Spring Boot logo

Spring Boot

5.4K
4.5K
555
5.4K
4.5K
+ 1
555
Create Spring-powered, production-grade applications and services with absolute minimum fuss
Spring Boot logo
Spring Boot
VS
Dropwizard logo
Dropwizard

related Spring Boot posts

Praveen Mooli
Praveen Mooli
Engineering Manager at Taylor and Francis · | 12 upvotes · 533K views
MongoDB Atlas
MongoDB Atlas
Java
Java
Spring Boot
Spring Boot
Node.js
Node.js
ExpressJS
ExpressJS
Python
Python
Flask
Flask
Amazon Kinesis
Amazon Kinesis
Amazon Kinesis Firehose
Amazon Kinesis Firehose
Amazon SNS
Amazon SNS
Amazon SQS
Amazon SQS
AWS Lambda
AWS Lambda
Angular 2
Angular 2
RxJS
RxJS
GitHub
GitHub
Travis CI
Travis CI
Terraform
Terraform
Docker
Docker
Serverless
Serverless
Amazon RDS
Amazon RDS
Amazon DynamoDB
Amazon DynamoDB
Amazon S3
Amazon S3
#Backend
#Microservices
#Eventsourcingframework
#Webapps
#Devops
#Data

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
Java
Java
JavaScript
JavaScript
Node.js
Node.js
nginx
nginx
Ubuntu
Ubuntu
MongoDB
MongoDB
Amazon EC2
Amazon EC2
Redis
Redis
Amazon S3
Amazon S3
AWS Lambda
AWS Lambda
RabbitMQ
RabbitMQ
Kafka
Kafka
MySQL
MySQL
Spring Boot
Spring Boot
Dropwizard
Dropwizard
Google Analytics
Google Analytics
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
GitHub
GitHub
Docker
Docker
Webpack
Webpack
CircleCI
CircleCI
Jenkins
Jenkins
Travis CI
Travis CI
Gradle
Gradle
Apache Maven
Apache Maven
Jira
Jira
notion.so
notion.so
Trello
Trello
Vue.js
Vue.js
Flutter
Flutter
Application & Data

Java JavaScript Node.js nginx Ubuntu MongoDB Amazon EC2 Redis Amazon S3 AWS Lambda RabbitMQ Kafka MySQL Spring Boot Dropwizard Vue.js Flutter

Utilities

Google Analytics Elasticsearch Amazon Route 53

DevOps

GitHub Docker Webpack CircleCI Jenkins Travis CI Gradle Apache Maven

Cooperation Tools

Jira notion.so Trello

See more

related Play posts

Alex A
Alex A
Founder at PRIZ Guru · | 3 upvotes · 123.9K views
atPRIZ GuruPRIZ Guru
Grails
Grails
Play
Play
Scala
Scala
Groovy
Groovy
Gradle
Gradle

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
Spring logo

Spring

2.2K
1.8K
974
2.2K
1.8K
+ 1
974
Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
Spring logo
Spring
VS
Dropwizard logo
Dropwizard

related Spring posts

Spring
Spring
Spring Boot
Spring Boot
Java
Java
IntelliJ IDEA
IntelliJ IDEA
Slack
Slack

Spring Spring-Boot Java IntelliJ IDEA Slack

See more
Dropwizard Metrics logo

Dropwizard Metrics

10
2
0
10
2
+ 1
0
Capturing JVM- and application-level metrics
    Be the first to leave a pro
    Dropwizard Metrics logo
    Dropwizard Metrics
    VS
    Dropwizard logo
    Dropwizard
    Node.js logo

    Node.js

    37.5K
    31.4K
    8K
    37.5K
    31.4K
    + 1
    8K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    Node.js logo
    Node.js
    VS
    Dropwizard logo
    Dropwizard

    related Node.js posts

    Nick Parsons
    Nick Parsons
    Director of Developer Marketing at Stream · | 34 upvotes · 509.7K views
    atStreamStream
    Stream
    Stream
    Go
    Go
    JavaScript
    JavaScript
    ES6
    ES6
    Node.js
    Node.js
    Babel
    Babel
    Yarn
    Yarn
    Python
    Python
    #FrameworksFullStack
    #Languages

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Nick Rockwell
    Nick Rockwell
    CTO at NY Times · | 29 upvotes · 641.6K views
    atThe New York TimesThe New York Times
    MySQL
    MySQL
    PHP
    PHP
    React
    React
    Apollo
    Apollo
    GraphQL
    GraphQL
    Node.js
    Node.js
    Kafka
    Kafka
    Apache HTTP Server
    Apache HTTP Server

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    ASP.NET logo

    ASP.NET

    13.4K
    682
    0
    13.4K
    682
    + 1
    0
    An open source web framework for building modern web apps and services with .NET
      Be the first to leave a pro
      ASP.NET logo
      ASP.NET
      VS
      Dropwizard logo
      Dropwizard

      related ASP.NET posts

      Greg Neumann
      Greg Neumann
      Indie, Solo, Developer · | 6 upvotes · 287.9K views
      Xamarin
      Xamarin
      .NET Core
      .NET Core
      Xamarin Forms
      Xamarin Forms
      ASP.NET
      ASP.NET
      Quasar Framework
      Quasar Framework
      Electron
      Electron
      Vue.js
      Vue.js
      TypeScript
      TypeScript

      Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

      This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

      But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

      I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

      Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

      See more
      Heroku
      Heroku
      Netlify
      Netlify
      Vue.js
      Vue.js
      Angular 2
      Angular 2
      React
      React
      ExpressJS
      ExpressJS
      vuex
      vuex
      Puppeteer
      Puppeteer
      ASP.NET
      ASP.NET
      #Heroku
      #Seo

      I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.

      See more
      Django logo

      Django

      9.5K
      7.4K
      2.9K
      9.5K
      7.4K
      + 1
      2.9K
      The Web framework for perfectionists with deadlines
      Django logo
      Django
      VS
      Dropwizard logo
      Dropwizard

      related Django posts

      Dmitry Mukhin
      Dmitry Mukhin
      CTO at Uploadcare · | 22 upvotes · 453.9K views
      atUploadcareUploadcare
      Django
      Django
      Python
      Python
      React
      React
      Ember.js
      Ember.js
      Preact
      Preact
      PostCSS
      PostCSS

      Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

      Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

      For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

      However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

      All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

      See more
      Node.js
      Node.js
      JavaScript
      JavaScript
      Django
      Django
      Python
      Python

      Django or NodeJS? Hi, I’m thinking about which software I should use for my web-app. What about Node.js or Django for the back-end? I want to create an online preparation course for the final school exams in my country. At the beginning for maths. The course should contain tutorials and a lot of exercises of different types. E.g. multiple choice, user text/number input and drawing tasks. The exercises should change (different levels) with the learning progress. Wrong questions should asked again with different numbers. I also want a score system and statistics. So far, I have got only limited web development skills. (some HTML, CSS, Bootstrap and Wordpress). I don’t know JavaScript or Python.

      Possible pros for Python / Django: - easy syntax, easier to learn for me as a beginner - fast development, earlier release - libraries for mathematical and scientific computation

      Possible pros for JavaScript / Node.js: - great performance, better choice for real time applications: user should get the answer for a question quickly

      Which software would you use in my case? Are my arguments for Python/NodeJS right? Which kind of database would you use?

      Thank you for your answer!

      Node.js JavaScript Django Python

      See more
      Rails logo

      Rails

      9.4K
      6K
      5.3K
      9.4K
      6K
      + 1
      5.3K
      Web development that doesn't hurt
      Rails logo
      Rails
      VS
      Dropwizard logo
      Dropwizard

      related Rails posts

      Zach Holman
      Zach Holman
      at Zach Holman · | 34 upvotes · 315.1K views
      React
      React
      Apollo
      Apollo
      Rails
      Rails
      JavaScript
      JavaScript

      Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

      But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

      But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

      Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

      See more
      Russel Werner
      Russel Werner
      Lead Engineer at StackShare · | 21 upvotes · 508.7K views
      atStackShareStackShare
      React
      React
      Glamorous
      Glamorous
      Apollo
      Apollo
      Node.js
      Node.js
      Rails
      Rails
      Heroku
      Heroku
      GitHub
      GitHub
      Amazon S3
      Amazon S3
      Amazon CloudFront
      Amazon CloudFront
      Webpack
      Webpack
      CircleCI
      CircleCI
      Redis
      Redis
      #StackDecisionsLaunch
      #SSR
      #Microservices
      #FrontEndRepoSplit

      StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

      Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

      #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

      See more