Re:Ask HN: How are you setting up your Java applications?
by ishbits on Friday October 26, 2012 @09:41PM
(#4705029)
I developed some test APIs and played with WebSocckets in play. One thing I didn't like, is like a WAR, it wants to be first level piece of software. However, I think this is an attitude I carry from embedding web services into projects years ago.. And I need to give in and develop things as web apps.
Scope is a service.. User interface for reporting and graphing, and an API for punting messages around (not instant messages or anything like that). And a database. And servers in the backend will need to talk to other peer servers in another data center.
Thanks for your input.
If you're planning to build the front-end with a lot of JS or Backbone-style interaction, you'll want an API anyway, so you might go with the last method of developing REST endpoints and just accessing them via JSON and Backbone. (This is the approach I'm taking on my most recently project, though Python is the backend, not Java).
Without knowing the scope of the project, whether there are customers, what kind of customers they are, etc., it's a little hard to make an informed decision, however one thing I didn't see was Play[1]. The last Java project I had was done in Play and I found it pretty easy to get up to speed on, and it's designed to act as a web framework. If you're looking for something new to learn, or an easy way to transition from systems development to web work, Play might be a fun transition for you.
[1] - http://www.playframework.org/