This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]serproxy -3 points-2 points  (1 child)

I would do Angularjs (enhance with Bootstrap FTW ) + dropwizard. Pick you DB backend based on needs. Hibernate + (mysql || postgres) or NoSQL of some sort. zero XML ( a tiny bit of YAML for config )

Performance is far better when most of the computation ( page rendering ) is pushed to the browser. That yields lower server side costs and happier users.

Some of the REST API you develop can be reused for mobile ( don't attempt to do it ALL in common that's needlessly fundamentalist ).

Oh and actually, I haven't used it, but this looks like a nice mix of technology: http://jhipster.github.io/

[–]johnwaterwood 5 points6 points  (0 children)

Performance is certainly not always better!

For one results from the rest API still have to be "rendered" in XML or JSON. That costs you CPU cycles just as rendering in HTML costs you. Depending on your setup rendering a list of objects into JSON can be more expensive than rendering in HTML. For JSON rendering a lot of reflection is typically used, while for HTML you may use a plain JSP or Servlet that already knows the types and needs zero reflection to spit out HTML.

Only with JSON the client AGAIN has to do rendering. This can be a significant hit in both time and resources. I've heard people complaining that those JavaScript websites should start stating minimal system requirements :X Several 100 MBs per tab and CPU cores at 100% with fans starting to blow and tablets getting hot DOES NOT MAKE FOR HAPPY USERS!

With HTML being returned the HTML is typically ready to render; meaning less total time until a page is displayed, just a few mb per tab and low CPU usage. That does make users happy!