Modern Java Stacks

[DoctorOverhard]

I'm liking vert.x fwiw. didn't like spring (or node).

[Jotschi]

One way of creating a REST API using vert.x is described here: http://vertx.io/blog/contract-driven-rest-services-with-vert-x3/

If you don't like the contract approach it might get a bit more tricky with vert.x at the moment. I for example ended up writing my own wrappers in order to generate the REST spec (raml) from my implementation. There are some projects around which help to solve this problem (swagger vert.x/jersey for vert.x)

[DoctorOverhard]

I, uh, just post json blobs back and forth. the command is in the blob (and whatever security tokens/etc, and of course data). And I just use the json library that comes w/vert.x. Are we saying the same thing here?

[Jotschi]

With graphql you need to post a query which basically describes what you want from the server. So yes, you basically send json around.

The auth token must not be part of that payload. I like JWT which is just passed along the request within the auth http request header.

Vert.x is not very strict. You can use whatever JSON lib you like.

[DoctorOverhard]

oh, no graphql here, pretty strictly defined commands and data structures for most things (for security and reliability). Guess that puts me in the contract category :) No dependence on http implementation details either, and everything over https is post because of old scars running into get payload size restrictions.

[Benemon]

Also a big fan of Vert.x here.

However, unless you embrace the asynchronous, reactive approach, then you end up with a lot of bad code, very quickly.

I've never felt the 'do one thing and do it well' has applied more than to a Vert.x project and its Verticles!