What would be the market life of a JVM based software framework? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

I saw how Struts 1 lasted from 2000 to 2013. I hear that people are moving from Struts 2 to Spring. But for a project that may need to be maintained for a decade or two, would it be advisable to opt for a framework or directly code with servlets and jquery? Can a system architecture really be designed keeping in mind a particular framework?

What really is the market life of a framework? Do the creators of the framework create it with the assumption that it would become obsolete in a decade?

Answer 1

My advice is to evaluate JVM web frameworks based on ~20 criteria that are important to you and your application. This includes technical categories (e.g. supports RESTFul, Ajax, i18n) and non-technical categories (e.g. Strength of community, number of books etc). Score each category (with weightings on categories that are more important to you) and pick the two winners.

Then prototype the top two, picking a problem that you know is risky/difficult for your project.

Matt Raible is the guy who taught most of us this approach, see him in action here: