51–60 of 88 posts
Everything work great. If you learn real work DW app, see my open source project.
Stack:
1. AngularJS 1.x as frontend
2. DW as REST backend
3. Hibernate as Data Access Layer
4. PostgreSQL as DB
Earlier quoted context omitted.
My greatest gripe with Java was the amount of crap one had to go through just to build a simple Rest API. When I saw DropWizard I thought it solved that need. Maybe it's time to get back into Java development...
If you love dealing with magic "comefrom" annotations, codegen that isn't debuggable, and foundational libraries that have to resort to bytecode manip to get stuff done, then go ahead.
Earlier quoted context omitted.
If you love dealing with magic "comefrom" annotations, codegen that isn't debuggable, and foundational libraries that have to resort to bytecode manip to get stuff done, then go ahead.
So, is the answer to just bail on Java forever? I haven't written anything legitimate in Java in about two years, but I don't remember it being that bad. For reference, what types of languages/frameworks do you like to work with?
Nice to see a 1.0 release. We've been using Dropwizard for various public and internal APIs for a couple of years and have been very happy with it. The components (jersey, jackson, coda hale metrics) are all very pleasant to work with, and generally have low-ceremony APIs that feel as productive as the ruby or python equivalents while providing the performance and operability of the JVM. It's not the fastest or most…
What JVM microframeworks would you recommend for streaming or async?
RatPack is a nice async microframework
See https://www.techempower.com/benchmarks/#section=data-r12&hw=...
Earlier quoted context omitted.
What JVM microframeworks would you recommend for streaming or async?
You can plug Quasar/Comsat in to get lightweight threads http://blog.paralleluniverse.co/2014/01/22/introducing-comsa... RatPack is a nice async microframework
Earlier quoted context omitted.
If you love dealing with magic "comefrom" annotations, codegen that isn't debuggable, and foundational libraries that have to resort to bytecode manip to get stuff done, then go ahead.
So, is the answer to just bail on Java forever? I haven't written anything legitimate in Java in about two years, but I don't remember it being that bad. For reference, what types of languages/frameworks do you like to work with?
Dropwizard is really just an opinionated bundling of sane Java libraries that don't suck, and is essentially tailor-made for the (quasi-)event-driven processing model of: 1. request comes in 2. do stuff here 3. response goes out While this may not sound very exciting, this is exactly what goes on in HTTP APIs. People these days use Node or Go for this kind of stuff, but Dropwizard makes it very pleasant to do it in J…
(For the record, I don't mean to offend anyone, but Spring Boot reminds me of the old truism about Visual Basic: "it makes easy things stupidly easy and the hard things impossible".)
To teams that you Dropwizard, what is your front end stack? Do you use Angular and communicate with proxy to dropwizard or do you do something which talks to Dropwizard API directly?
Earlier quoted context omitted.
So, is the answer to just bail on Java forever? I haven't written anything legitimate in Java in about two years, but I don't remember it being that bad. For reference, what types of languages/frameworks do you like to work with?
If you want to venture back to the JVM, Kotlin offers a very good middle ground between Java and Scala.