Need advice about which tool to choose?Ask the StackShare community!

Dropwizard

284
317
+ 1
179
Phalcon

225
269
+ 1
353
Add tool

Dropwizard vs Phalcon: 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; Phalcon: Web framework delivered as a C-extension for PHP. Phalcon is a web framework implemented as a C extension offering high performance and lower resource consumption.

Dropwizard and Phalcon belong to "Frameworks (Full Stack)" category of the tech stack.

"Quick and easy to get a new http service going" is the primary reason why developers consider Dropwizard over the competitors, whereas "Fast" was stated as the key factor in picking Phalcon.

Dropwizard and Phalcon are both open source tools. It seems that Phalcon with 9.74K GitHub stars and 1.78K forks on GitHub has more adoption than Dropwizard with 7.25K GitHub stars and 3.04K GitHub forks.

According to the StackShare community, Dropwizard has a broader approval, being mentioned in 51 company stacks & 12 developers stacks; compared to Phalcon, which is listed in 28 company stacks and 15 developer stacks.

Decisions about Dropwizard and Phalcon
Hampton Catlin
VP of Engineering at Rent The Runway · | 7 upvotes · 139.3K views

Starting a new company in 2020, with a whole new stack, is a really interesting opportunity for me to look back over the last 20 years of my career with web software and make the right decision for my company.

And, I went with the most radical decision– which is to ignore "sexy" / "hype" technologies almost entirely, and go back to a stack that I first used over 15 years ago.

For my purposes, we are building a video streaming platform, where I wanted rapid customer-facing feature development, high testability, simple scaling, and ease of hiring great, experienced talent. To be clear, our web platform is NOT responsible for handling the actual bits and bytes of the video itself, that's an entirely different stack. It simply needs to manage the business rules and the customers experience of the video content.

I reviewed a lot of different technologies, but none of them seemed to fit the bill as well as Rails did! The hype train had long left the station with Rails, and the community is a little more sparse than it was previously. And, to be honest, Ruby was the language that was easiest for developers, but I find that most languages out there have adopted many of it's innovations for ease of use – or at least corrected their own.

Even with all of that, Rails still seems like the best framework for developing web applications that are no more complex than they need to be. And that's key to me, because it's very easy to go use React and Redux and GraphQL and a whole host of AWS Lamba's to power my blog... but you simply don't actually NEED that.

There are two choices I made in our stack that were new for me personally, and very different than what I would have chosen even 5 years ago.

1) Postgres - I decided to switch from MySql to Postgres for this project. I wanted to use UUID's instead of numeric primary keys, and knew I'd have a couple places where better JSON/object support would be key. Mysql remains far more popular, but almost every developer I respect has switched and preferred Postgres with a strong passion. It's not "sexy" but it's considered "better".

2) Stimulus.js - This was definitely the biggest and wildest choice to make. Stimulus is a Javascript framework by my old friend Sam Stephenson (Prototype.js, rbenv, turbolinks) and DHH, and it is a sort of radical declaration that your Javascript in the browser can be both powerful and modern AND simple. It leans heavily on the belief that HTML-is-good and that data-* attributes are good. It focuses on the actions and interactions and not on the rendering aspects. It took me a while to wrap my head around, and I still have to remind myself, that server-side-HTML is how you solve many problems with this stack, and avoid trying to re-render things just in the browser. So far, I'm happy with this choice, but it is definitely a radical departure from the current trends.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Dropwizard
Pros of Phalcon
  • 27
    Quick and easy to get a new http service going
  • 23
    Health monitoring
  • 20
    Easy setup
  • 19
    Metrics integration
  • 18
    Good conventions
  • 14
    Lightweight
  • 14
    Good documentation
  • 12
    Java Powered
  • 10
    Good Testing frameworks
  • 7
    Java powered, lightweight
  • 4
    Simple
  • 4
    Scalable
  • 3
    Great performance, Good in prod
  • 2
    Open source
  • 2
    All in one-productive-production ready-makes life easy
  • 64
    Fast
  • 54
    High performance
  • 37
    Open source
  • 35
    Fast and easy to use
  • 32
    Scalable
  • 23
    Versatile
  • 22
    Fiexble
  • 20
    Automatic routing
  • 19
    It is easy and fast
  • 17
    Is very good
  • 9
    Dependency injection
  • 9
    Low overhead
  • 6
    Awesome
  • 2
    Easy and fast
  • 1
    Great for API
  • 1
    Clean Architecture
  • 1
    Modularity
  • 1
    Easy Setup
  • 0
    Very customizable

Sign up to add or upvote prosMake informed product decisions

Cons of Dropwizard
Cons of Phalcon
  • 2
    Slightly more confusing dependencies
  • 1
    Not on ThoughtWorks radar since 2014
  • 4
    Support few databases
  • 2
    Very bad documentation

Sign up to add or upvote consMake informed product decisions

What is Dropwizard?

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.

What is Phalcon?

Phalcon is a web framework implemented as a C extension offering high performance and lower resource consumption.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Dropwizard?
What companies use Phalcon?
See which teams inside your own company are using Dropwizard or Phalcon.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Dropwizard?
What tools integrate with Phalcon?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Dropwizard and Phalcon?
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 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
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
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
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.
See all alternatives