Dropwizard VS Feign

I'm trying to set up a simple RESTful API with dropwizard that does some basic CRUD with a postgresql database. I've managed to get some endpoints working with dummy responses following the documentation, but I am now quite stuck when it comes to implementing the database functionality. The page about JDBI3 doesn't really help because the example usage doesn't match with the example app in the repository, where the code looks quite different and with no recent commits. It seems to assume prior knowledge of all of these libraries (which I don't have).

You might like Dropwizard then.

Dropwizard is a nice opinionated veneer over all the standard bits and pieces. https://www.dropwizard.io

A new, Feign client, to make the get request to https://example.com/themes. This client will expose a get() method.

The actual project for feign is OpenFeign https://github.com/OpenFeign/feign . Spring comes with it's own starter . Add below dependency to the project

Find a community/project that interests you, I've gone with feign. Head on into the issues tab, and you'll see all the potential contributions you could make. Starting out, it's a good idea to search for tags like "bug", or "good first issue".

Feign has support for what you're looking for. https://github.com/OpenFeign/feign/tree/master/jaxrs2

feign-spring4 gives you a type safe client proxy of an interface annotated with Spring MVC annotations.

At the risk of doxxing myself, I'm a contributer attempting to fix this issue with this pr. The project has existed for a while now, and since I'm not part of the openfeign team, so the final solution they end up using isn't up to me. So there's technical debt to deal with (how the project is built and tested currently) and whether or not multi-release jars are the best solution in this case.