High Scalable and Distributed Architecture

This article describes how to achieve high scalability with Java EE EJB 3.0 and Spring Framework. Also how this hybrid solution can be scalable in a cloud space.

In an Enterprise world, Spring Framework with some standard ORM tool like Hibernate gained considerable acceptance as a light-weight architecture for mid size applications. Also in Java EE 5 specification, major changes has been done on component architecture, tried overcome the gaps like IoC, ORM etc.

Concept of IoC is still immature in the Java EE 5 and the flexibility, AOP, and relative strengths of Spring and ORM tool like Hibernate to further improve the productivity and quality of any web based applications. As JPA (part of Java EE 5) specification suggest pluggable design so we can use any ORM tool (compatible of JPA) in any application server like IBM WebSphere uses Apache OpenJPA as a default provider but Hibernate can easily be pluggable.

This article demonstrates how to build a highly scalable application with hybrid technology like EJB 3.0, Spring 3.0.x, and Hibernate. Also Spring Framework has its own remoting APIs and options but EJB is a standard specification and can easily be migrated across the application servers.
By designing a flexible and component architecture, the application will use the power of EJB 3.0, IoC & APO of Spring 3.0.x and ORM capability of Hibernate.

For more detail, visit my published article on theserverside website.

JSF, Spring & Hibernate - Light weight Architecture

Recently I have finished one assignment on J2EE technology and it was the good experiences.

Project was typical web-based with database driven. After studying the application I decided to use JSF in front end, spring in middle and hibernate for interacting with database.
Though I haven't worked on JSF & Spring prior to this project and my team was also new but I took the challenge also.

I decided for JSF because the client wants rich GUI. As soon as we started and get into the project I realized that learning curve of JSF is very high. At that time team was struggling very hard to get hold of it. And the result was we delivered first module 10 days after the deadline.

As time passes, we got the hold of JSF and delivered the all the modules on/before time. We had used various in-build components available on net which actually saved most of our time.
We had also met the performance benchmark of client.

So what I feel for small & middle level projects you can use "JSF-Spring-Hibernate" because:
1. You will get good in build components in JSF
2. Spring helps you in wring objects and it has a good feature of AOP
3. Hibernate is a good ORM tool with lots of feature.

Apart from good learning on "JSF-Spring-Hibernate" framework I also learned that you should also keep in mind while deciding on tools/frameworks that how is team and what is the time frame.

So guys try to use "JSF-Spring-Hibernate" framework and share your experiences.