ReactJS + DropWizard + JDBI (or JOOQ) if you like JAX-RS. ReactJS + Spark framework (or Vert.x 3 or Ratpack) + JDBI if you don't like JAX-RS. I don't like JAX-RS, but it is hard to beat DropWizard if you do.
[deleted]
Ask HN: What stack would you use to build a CRUD web app on the JVM today?
41–50 of 213 posts
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#42I would not start with technology stack and build around them. You look at your use cases and build out. Pick your frameworks and databases judiciously and as late as possible. Read: https://blog.8thlight.com/uncle-bob/2012/05/15/NODB.html Read: http://www.amazon.co.uk/Growing-Object-Oriented-Software-Gui... [EDIT] Removed the unnecessary/unhelpful opening statement.
I think "JVM Web app that does CRUD" is sufficiently narrow to consider that your use case, and pick a technology based on that use case.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#43I'm building something with React + Relay + Sangria and it's working out well so far. There's a sample sangria project showing how to use it on akka-http, and if you write a pure web app like this, you could serve the javascript client from somewhere dumb like S3. Plus with this stack you can plug in react-native apps as well once your server is written.
how are you running React on the JVM - Are you using Nashorn or Rhino here?
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#44Spring MVC + Hibernate. I'm familiar with those libraries and they provide almost everything I usually need. For frontend I would choose either JSP or Thymeleaf, both are good, depends on your taste and whether you're writing HTML markup. Another option is a JavaScript-powered SPA website. You have plenty of choices there. And I highly suggest using Intellij Idea Ultimate + JRebel. Those technologies provide tremendo…
For people whose impression of Spring and Hibernate was formed a decade ago, its really worth another look now. You can completely manage them with annotations in your code and lots of the boilerplate will be generated for you based on naming conventions. JHipster ( https://jhipster.github.io/ ) provides a Yeoman generator to make a basic project template as well as generate entities and screens using an Angular, Spr…
It doesn't change my impression much if the answer to "lots of boilerplate" is to use another tool to generate it automatically...
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#45I'm building something with React + Relay + Sangria and it's working out well so far. There's a sample sangria project showing how to use it on akka-http, and if you write a pure web app like this, you could serve the javascript client from somewhere dumb like S3. Plus with this stack you can plug in react-native apps as well once your server is written.
how are you running React on the JVM - Are you using Nashorn or Rhino here?
Sangria is scala. React is the client in the browser. That doesn't run on the JVM.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#46I would not start with technology stack and build around them. You look at your use cases and build out. Pick your frameworks and databases judiciously and as late as possible. Read: https://blog.8thlight.com/uncle-bob/2012/05/15/NODB.html Read: http://www.amazon.co.uk/Growing-Object-Oriented-Software-Gui... [EDIT] Removed the unnecessary/unhelpful opening statement.
Just because uncle Bob says something doesn't mean it's true. Frameworks and stacks provide templates for building CRUD apps. Building CRUD apps (read: database skins) isn't a big technological challenge most of the times anyway. So picking a stack that abstracts most of it for you could be a great help to only focus on the parts you care about. Not every project requires astronaut architecture and grand design. Half…
My inclusion of these two reading resources were only meant as examples. The reader is still required to make their own mind up.
I haven't suggested astronaut architecture; the question didn't indicate the size/scale/importance either.
50% of the internet runs perfectly fine without consideration...wow! Have you looked at all the source code yourself to make such a ridiculous conclusion.
Tooling does matter, but I'm suggesting the point of focus to start with is the requirements.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#47I would not start with technology stack and build around them. You look at your use cases and build out. Pick your frameworks and databases judiciously and as late as possible. Read: https://blog.8thlight.com/uncle-bob/2012/05/15/NODB.html Read: http://www.amazon.co.uk/Growing-Object-Oriented-Software-Gui... [EDIT] Removed the unnecessary/unhelpful opening statement.
Yes/No, depends on many factors IMHO. Mostly on the person/team that needs to build/use it. We know nothing of OP's case so the best thing we can do is trying to answer his question instead of answering to go read some lengthy book. OP might be in a team that needs to develop an API for a product that will be deployed to millions of people(I doubt it) or could be someone that just wants to know what is the current fa…
fair comment. I will add though, spring, or hibernate, or play, or [pick your framework here] will also require reading.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#48First of all, I have to agree with dommer. You pick the stack depending on the use case.
That being said, in most use cases I've encountered I would've gone with a REST API on the server for CRUD operations and an SPA framework on the UI side. I've found that the use of a classical UI Framework like Play, Grails or JSF make seperation of UI and business logic harder, rather than easier. Especially Grails is a huge vendor lock in and the framework leaks through all layers.
To "scaffold" your REST+SPA application, I've found Spring Datas automagic generation pretty useful, but you're free to use any technology you like.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#49Earlier quoted context omitted.
how are you running React on the JVM - Are you using Nashorn or Rhino here?
Sangria is scala. React is the client in the browser. That doesn't run on the JVM.
can you talk a bit more ? How do you write your views and integrate them with sangria. I'm coming from nodejs .. where everything is JS, so I'm trying to understand how this stack works.
Re: Ask HN: What stack would you use to build a CRUD web app on the JVM today?
#50I would not start with technology stack and build around them. You look at your use cases and build out. Pick your frameworks and databases judiciously and as late as possible. Read: https://blog.8thlight.com/uncle-bob/2012/05/15/NODB.html Read: http://www.amazon.co.uk/Growing-Object-Oriented-Software-Gui... [EDIT] Removed the unnecessary/unhelpful opening statement.
[deleted]