If you
have built database-oriented web applications in the past and wondering now
which is the best framework to build going ahead, the below classification
might help. I tried creating a decision tree for some of the most popular
frameworks.
As you can see in one extreme it's
the Java based standard (JEE) frameworks and at the other extreme it's the
non Java, non sharing (no servlet session) completely new frameworks and in the middle is the Spring MVC and Grails.
Whatever you pick between the HTML/Javascript and your backend/middleware, it’s important to know how these frameworks differ at a fundamental level which can affect scalability, performance, developer productivity, cost etc.
It's important to note that these
frameworks are just not presentation frameworks, they extend to use an ORM
framework (mostly hibernate) and have their own build tool, ide etc. Each
one of them pretty much extends to a platform and will support cloud
deployment.
Interesting video here on why twitter is moving from Ruby on Rails to JVM.
Now time for the new debate how much client side MVC and how much Server side MVC? / REST API?
Interesting video here on why twitter is moving from Ruby on Rails to JVM.
Now time for the new debate how much client side MVC and how much Server side MVC? / REST API?
No comments:
Post a Comment