Social Networking sites normally have 4 different functions:

   1. Networking;
   2. Social;
   3. Identity; and
   4. Sharing

Networking - Here networking is meant in the business sense of the word. In the real world this would be like when two executives meet and exchange business cards at an industry seminar. What is taking place is formal, relatively impersonal and goal orientated relationship creation.

Social - If something has a Social function it means there is a strong human and informal dimension to the interaction. Personalities are on display and personal relationships created. Social could thus include people doing things for fun: Like playing tennis for instance. But it does not necessarily mean it is not serious.

Identity - means building meaning and displaying what and who you are.

"Sharing" is of course in reality a misnomer. To many observers, users seemingly do things on the Internet for free as if they want nothing in return. This is not accurate. In fact this gift giving is actually self publishing – for egotistical and status reasons. They do it because they want recognition. For the purposes of this post we will keep on calling it by its popular name: "sharing".

"Revenue Sharing" or "rewarding": The new web 3.0 concept - This is about revenue sharing  with the users who put in content and the popularity of the content.

This people focus of the web is a set of media technologies that enable people to get things from each other that they used to get from big institutions. So web 3.0"s advances will still revolve - at it"s essence - around empowering people

 The Framework consists of Plugable installable modules with independent DB which will seamlessly work with each other.

    * To what extent should the users form relationships or ties?;
    * Should they be weak or strong?
    * To what extent should the site allow socializing?; and
    * To what extent should users be able to express their identity; and
    * Should this identity be real?
    * What content do you want your users to generate?
    * And how do users find out of new UGC content that might interest them?

 The Genex Technology Stack is based on the latest trends in technology, architecture which had been proved to be robust and stable, and used in most of the Product Application development today.

The language used for building this stack is Java 6.0 which is quite stable and had been proved to have improved the stability of the Applications build-up.

Middle-tier layer:

The Middle-tier of the Genex Technology Stack is based on the POJO-based programming model. This removes the application server dependency.

Spring provides a light-weight solution for building enterprise-ready applications, while still supporting the application to continue running on the technologies like application server, JMS, JTA transaction support, security including authentication and authorization and so forth. It can also optionally allow us to deploy the application on web server for example, without limiting any enterprise level features. It helps switching these technologies declaratively without even touching the code and business logic in general. It also helps to introduce new interceptor declaratively without touching core business classes. For example, it is very easy to introduce performance interceptor to measure the targeted methods performances without touching any of the business classes in the application. It does this by enabling a POJO-based programming model that is applicable in a wide range of environments.

There are many advantages of moving to Servlet container:

Lower cost of ownership. Our customers don’t need to buy application costly server licenses.

Simplified development and increased productivity.

Simplified 3rd party upgrades. Today we spend lot of time in each release to certify application server version and there is lot of development cost associated with it.

Hot Deployment. This will simplify the developer debugging time.

String implements the IOC (Inversion of control) design pattern. It is a lightweight container and the objects are managed using an external XMl configuration file. Reference to a dependent object is obtained by exposing a JavaBean property.

IOC is a design pattern that externalizes application logic so that it can be injected into client code rather than written into it. Use of IOC in Spring framework separates the implementation logic from the client.

The transaction handling is done beautifully in Spring. It can integrate major persistence frameworks and offer a consistent exception hierarchy.

A flexible MVC web application framework, built on core Spring functionality. This framework is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI. Note that a Spring middle tier can easily be combined with a web tier based on any other web MVC framework, like Struts, WebWork, or Tapestry.

Integration with Toplink, Hibernate, JDO, and iBATIS SQL Maps: in terms of resource holders, DAO implementation support, and transaction strategies. First-class Hibernate support with lots of IoC convenience features, addressing many typical Hibernate integration issues. All of these comply to Spring"s generic transaction and DAO exception hierarchies.

The Business Logic is implemented using the POJOs which are independent of the framework and we can replace the Spring for any other IOC container.

Presentation Layer:

Struts:
Apache Struts is an open source Java framework used for building web applications based on the servlet and JavaServer Pages (JSP) technologies.Struts is more established and more stable MVC2 framework at this time.While the Struts framework is not completely unique, it provides some key benefits:

• Based on a Model 2 MVC implementation.
• Supports Java"s "Write Once, Run Anywhere" philosophy.
• Supports different model implementations (JavaBeans, EJB, etc.).
• Support for internationalization (I18N).
• Includes a rich set of JSP tag libraries.
• Contains many extension points for customization.
• Supports different presentation implementations (JSP, XML/XSLT, JavaServer Faces).

Persistence Layer:

Ibatis: Like other persistence layers, iBATIS strives to ease the development of data-driven applications by abstracting the low-level details involved in database communication (loading a database driver, obtaining and managing connections, managing transaction semantics, etc.), as well as providing higher-level ORM capabilities (automated and configurable mapping of objects to SQL calls, data type conversion management, support for static queries as well as dynamic queries based upon an object"s state, mapping of complex joins to complex object graphs, etc.). The iBATIS approach to this is very straightforward: use XML to loosely couple your Java objects and SQL commands.

Please Contact us to discuss your JAVA Software Application development requirement.