gwizard

A modular toolkit for building web services with Guice, inspired by DropWizard (by gwizard)

Gwizard Alternatives

Similar projects and alternatives to gwizard

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better gwizard alternative or higher similarity.

gwizard reviews and mentions

Posts with mentions or reviews of gwizard. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-22.
  • The Reason Java Is Still Popular
    2 projects | news.ycombinator.com | 22 Sep 2022
    Here's what I generally use when doing greenfield development in Java:

    https://github.com/gwizard/gwizard

    I wrote it, so feel free to consider me biased. That said, "wrote" is a strong word, it just glues some other projects together with Guice. Not much actual code there. Which may be the answer to your question - if you asked me what's wrong with other frameworks, "too much code" is a decent answer.

  • Ask HN: What is a modern Java environment?
    22 projects | news.ycombinator.com | 29 Mar 2022
    I have been thinking of writing up a series of articles on this. Without going into too much detail:

    * IDEA

    * Deploy on Google App Engine, Digital Ocean App Platform, Heroku, Elastic Beanstalk, etc - get out of the ops business entirely.

    * Guice as the backbone, no Spring/Boot. I wrote a tiny dropwiard-like "framework" to make this easier: https://github.com/gwizard/gwizard but there's a laughable amount of code here, you could build it all from scratch with minimal effort. This is about as lightweight as "frameworks" get because Guice does the heavy lifting.

    * JAX-RS (Resteasy) for the web API. IMO this is the best part of Java web development. HTTP endpoints are simple synchronous Java methods (with a few annotations) and you can test them like simple Java methods.

    * Lombok. Use @Value heavily. Cuts most of the boilerplate out of Java.

    * Junit5 + AssertJ. (Or Google Truth, which is almost identical to AssertJ).

    * Use functional patterns. Try to make all variables and fields final. Use collections streams heavily. Consider vavr.io (I'll admit I haven't it in anger yet, but I would in a new codebase).

    * StreamEx. Adds a ton of useful stream behavior; I don't even use basic streams anymore.

    * Guava. There's just a lot of useful stuff here.

    * For the database, it really depends on what you're building. Most generic business apps, postgres/hibernate/guice-persist/flyway. Yeah, folks complain about hibernate a lot but it's a decent way to map to objects. Use SQL/native queries, don't bother with JPQL, criteria queries, etc.

    * Hattery for making http requests (https://github.com/stickfigure/hattery). This is another one of mine. I make zillions of http requests, functional/immutable ergonomics really matter to me.

    * Github actions for CI.

    * Maven for the build. Yes, it's terrible, except for every other build system is worse. Gradle seems like it should be better but isn't. I'd really love some innovation here. Sigh.

Stats

Basic gwizard repo stats
2
110
6.2
2 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com