Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Java REST framework Dropwizard 1.0 released

dropwizard.io

Post reply on HN
Print view View original

31–40 of 88 posts

Re: Java REST framework Dropwizard 1.0 released

#31

Post by asdf1234 »

cle wrote: post #26
alexbanks wrote: post #22

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.

Yes. Most of the unnecessary complexity has just been moved from bad APIs with XML configuration to bad APIs with runtime scoped annotations, code generation and byte code manipulation. It's still a huge mess.

Re: Java REST framework Dropwizard 1.0 released

#32

Post by teen »

dozzie wrote: post #5

Funny that everybody rush for REST framework, while most of the time people cramming REST in their applications need less "read, upload, replace, delete" operation model and more "normal functions, except called remotely" provided by RPC. But RPC-over-HTTP (XML-RPC, JSON-RPC, or even Thrift) is a problem solved long ago, so it's not sexy enough, I think.

Couldn't agree more. REST is just a very leaky abstraction layer, when what you really want is RPC, with some reusable / composable typed models.

Re: Java REST framework Dropwizard 1.0 released

#33

Post by nu2ycombinator »

dozzie wrote: post #25
nu2ycombinator wrote: post #21

Earlier quoted context omitted.

REST is like set of best practices to design API end points like define resource as end point and map standard HTTP methods to certain operations. This makes it easy and leads to a standard in API designing. And underlying technology can be RPC or servlets too. For example define end point "/user" and client knows how to create update or delete user where as before Rest these used to be different end points for each…

More like set of worst practices. You have some API exposed in plenty of endpoints instead of one, and on top of that you embed one of the call arguments in the URL itself. And no, it doesn't make designing API easier if you preallocate "read", "create", and "delete" operations to separate HTTP methods, and then put all the other operations in POST. "Create" and "delete" in many cases don't even make any sense to gua…

Well there are no hard and fast rules. Any set of best practices are opinionated. You can have different of opinions if they are not suited for your use case. All the REST frameworks you found are designed around the those ideas. For making your APIs rest you do not need any framework you can design your APIs along those guidelines. Again how far your apis need to be REST complaint again it is upto common sense.

Re: Java REST framework Dropwizard 1.0 released

#34

Post by einrealist »

spapas82 wrote: post #7

Dropwizard is great for REST APIs (... as the title says). However if you want to use traditional views (MVC, html templates, security, forms etc) then please check something else (I tried it and lost many hours -- in the end I still couldn't do even basic things). For traditional web development, I recommend spring-boot which is almost as easy as dropwizard, it also doesn't need an application container and fully su…

We do our "MVC" stuff with Dropwizard. There are some minor quirks (like validation). But we find it suitable enough for how we build our applications. The upcoming javax.mvc standard will probably find its way into Jersey and Dropwizard. For the views, we use Freemarker (Thymeleaf was too slow and less extensible).

Re: Java REST framework Dropwizard 1.0 released

#35

Post by batbomb »

alexbanks wrote: post #22
niftich wrote: post #11

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…

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

Jackson+Jersey+Jetty is 95% of the way there for most things, it's not bad at all.

Re: Java REST framework Dropwizard 1.0 released

#37

Post by wmfiv »

abalone wrote: post #28
necubi wrote: post #3

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?

Akka HTTP is very nice.

Re: Java REST framework Dropwizard 1.0 released

#39

Post by dustingetz »

teen wrote: post #32
dozzie wrote: post #5

Funny that everybody rush for REST framework, while most of the time people cramming REST in their applications need less "read, upload, replace, delete" operation model and more "normal functions, except called remotely" provided by RPC. But RPC-over-HTTP (XML-RPC, JSON-RPC, or even Thrift) is a problem solved long ago, so it's not sexy enough, I think.

Couldn't agree more. REST is just a very leaky abstraction layer, when what you really want is RPC, with some reusable / composable typed models.

I don't know, RPC is declaring for no abstraction at all, just raw access to code that can do anything. REST provides strong abstractions, they are just slow, and to make the app fast we have to compromise them. But that's the same for relational databases and ORM; I think really REST isn't the problem, but instead SQL. And RPC is like writing bits with butterflies.

Re: Java REST framework Dropwizard 1.0 released

#40

Post by avita1 »

asdf1234 wrote: post #31
cle wrote: post #26

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.

Yes. Most of the unnecessary complexity has just been moved from bad APIs with XML configuration to bad APIs with runtime scoped annotations, code generation and byte code manipulation. It's still a huge mess.

I use Dropwizard in my day-to-day and I've never ran into any code generation or byte code manipulation.
Post reply on HN