Skip to main content

Java Web Framework Comparison

Wikipedia has listed over 85 web applications frame works with Java based on the top – 28. Below table lists of most widely used web Application Frameworks products available today.

Product

what type of project is best fit?

Struts 2

The new version Struts 2.0 is a combination of the Sturts action framework and Webwork (a total redesign). Struts2 may a good fit for an enterprise application when there is existing Struts resource and projects of medium complexity.

Spring MVC

Good choice for medium sized project. Convention-based defaults for controllers, model object names, and view resolves. Spring MVC addresses request-driven processing at the HTTP level. It does not aim to provide a component model like JSF.

Stripes

An open source web application framework based on MVC pattern. It aims to be a more lightweight framework than Struts by using annotations and generics that were introduced in Java 1.5, to achieve "convention over configuration".

JSF

JSF will be a better fit if the need is to build a complex web application with lots of user interaction and traffic. JSF is the choice when you want to build desktop-like functionality to the browser within the standard specification and large amounts of third-party features. JSF places heavy emphasis on being able to scale requirements and complexity well. JSF may be too heavy weight for small to medium web applications.

GWT

Google Web Toolkit is an open source a development toolkit for building and optimizing complex browser-based applications. GWT is used by many products at Google, including Google Wave and Google AdWords.

Tapestry5

Tapestry emphasizes simplicity, ease of use, and aims to avoid forcing programmers to create enormous blocks of "glue code", using Convention over Configuration paradigm.

Popularity Analysis

Below is a trend analysis that shows the requirement for major Web Application frame work (source: http://www.indeed.com ) over the last 5 years.

job-trends-stripes-gwt-tapstry

job-trends-struts-spring-jsf

Java Server Face (JSF) is NOT a good fit for all web applications.JSF will be a better fit if the need is to build a complex web application with lots of user interaction and traffic.

JSF can be an over kill for small web applications because of it complexity and learning curve.

Popularity analysis shows that new frame works like GWT, Spring MVC and Struts2 has better industry acceptance than JSF.

Comments

Popular posts from this blog

SAAS Simple Maturity Model

There are two architectural models – commonly referred as SAAS Maturity models- that describe the transition of a service to what is called Multi-tenant efficient, highly scalable application. The SAAS Maturity model described by Microsoft has four distinct stages and is illustrated below. Another similar well-known model for SaaS-maturity is known as Forrester-model but adds another stage known as "Dynamic Business Apps-as-a-service". The three key Attributes of a SAAS Architecture: Configurability: Metadata used to configure the way the application behaves for customers Multi-tenant Efficiency : Maximizing the sharing of resources across tenants Scalability: Maximizing concurrency, resource efficiency SAAS Simple Maturity Model (Microsoft, 2006) SaaS Maturity Model (Forres

SpringBoot : Performance War

Reactive Systems are designed to address challenges posed by modern software systems - the challenges related to large number of users and high throughput. Reactive systems are expected to be highly responsive, resilient, elastic and message driven. In this article we will: Build a set of fully non-blocking REST API using SpringBoot 2.0, WebFlux and Reactive Redis. Performance test the above Reactive APIs against the traditional non-reactive APIs. The code used in this example can be downloaded from GitHub Step 1: Create a skeleton Reactive WebFlux SpringBoot project Create a SpringBoot maven project using - https://start.spring.io/ Add the following dependencies: spring-boot-starter-web spring-boot-starter-data-redis spring-webflux spring-boot-starter-data-redis-reactive Refer to the dependencies in pom.xml Step 2: Create Domain Objects The demo project uses the domain objects Customer and Account . A customer can have multiple accounts.