Web 2.x Blog

The above represents a conceptual architecture for a Enterprise 2.0 collaboration application.

• Loose Integration - This allows reuse of components and allows selective hosted SaaS offering to the public. (Why pay for the whole package when I only need a small part of it ) . i.e Basecamp does this with their chat component.

  For the Enterprise, this allows managers or knowledge workers to selectively choose to package the mini-applications that is relevant to their work.

• Application 1 / SaaS 1 … Application n / SaaS n - This represents each functionality of the overall application to be written in terms of mini applications or independent SaaS-es. This can represent a blog, wiki, project management tool…etc. Advantage of this is allowing the user to mix and match their choice of SaaS-es in a package.

• REST XML/Web Services API - For the public, this allows users to mashup content received via API calls over the net in their application. i.e. Basecamp allows milestone retrievals via API call. For the Enterprise, this allows an employee to securely mashup a information specific portlet for themselves.

• Consolidated User Interface - Specific RIA technologies such as Adobe Flex/MS Silverlight can be used to build a consolidated interface to allow a consolidated view of the overall 1..n applications in it.

I would also like to direct you to another Enterprise 2.0 architecture that shows relationships between the different SLATE elements in a Enterprise 2.0 application.

Tags: Architecture, Enterprise 2.0, SaaS, Web 2.0