[subsection1h]

  > My manager called Rails passé this morning [...]
  > our team to start using a single page architecture

What server-side framework does your manager think should be used with the client-side framework?

  > a trend just like rails was a year ago.

Rails was a trend a year ago (2012)? Out of curiosity, what was Rails between 2005 and 2011?

[binofbread]

He seems to be in the "if it works now, why change it?" camp. So at the moment that means using Java Server Faces on the front end. I haven't had much exposure to the server-side, but I'm so not sure there is any good framework in place as it's closely coupled with the front end logic.

Your second comment is a good one. What I think he meant by "trend" was that last year Rails was what all the architects and leaders at the company were pushing for. His argument was that this year it's the same thing except with single page architecture (Backbonejs in this case).

[GFischer]

From an entirely outside experience, I saw at the company I work for a very bad experience with a project where the team pushed for a single page application - they got delayed for months because of the technology, the problem was not single page applications in themselves, but that they seriously underestimated the learning curve and they were absolute novices (no-one had prior experience in SPA). And I definitely believe they could have cut months from the development time by sticking to known tech.

For a company where development is not core, I wouldn't recommend it, but if the company is a tech company, I would evaluate devoting resources to learning single page applications and doing some pilot projects, then leveraging the experience and pushing it into the main projects if applicable :) .