Enterprise 2.0 Cloud Computing & Service Oriented Architecture (SOA)
Integrating Internet Principals In Your Intranet
You may of heard someone in your office say something like “20% of the people are doing 80% of the work”. This is known as The Pareto Principle, aka the 80-20 Rule. This principal will also apply to the future architecture of the internet composed of 80% Consumers and 20% Producers supported by “Linked Data” This paradigm shift in information architecture will be fuled by the adoption of using widgets, gadgets, and apps to connect information.
Enterprise 2.0 App Stores
- What if you had an Enterprise 2.0 App created from SharePoint?
- What if you had an Enterprise 2.0 App for email?
- What if you had Enterprise 2.0 Apps for your team blog, wiki, graphs, activity streams, …?
- What if all these apps were displayed as Widgets in your Enterprise 2.0 Dashboard?
Enterprise 2.0 App Store Architecture
Most organizations have a difficult time measuring the use of their Information Technology. Some organizations can measure enough to know that moving at least some technology to the cloud makes sense. Businesses can also realize the benefits from the concept of cloud computing through Enterprise 2.0 App Store Architecture.
What is an Enterprise 2.0 App?
An Enterprise 2.0 App is “a snippet of code that is shared to serve a specific purpose”. This “App” can be displayed and used on smart phones, mobile devices, desktops, web browsers, dashboards, or other applications.
Where is the App Stored?
Apps can be stored internally or externally.
Internal Apps, Widgets, & Gadgets
Internal apps are hosted and used by the owner, usually in the same domain, therefore the level of trust is higher.
External Apps, Widgets, & Gadgets
External apps are hosted outside the domain and usually by a third party. The level of trust is lower, therefore the proper security measures should taken. All developers should know how to build, design and test the security of web applications and web services.
Using a Web Proxy
All modern web browsers impose a security restriction on network connections, which includes calls to XMLHttpRequest. This restriction prevents a script or application from making a connection to any web server other than the one the web page originally came from (Internet Explorer will allow cross-domain requests if the option has been enabled in the preferences). If both your web application and the XML data that application uses come directly from the same server, then you do not run into this restriction. See the PHP Web Proxy code below and learn more about AJAX Web Proxies here.
You should also see this article: “Restricting Access to your AJAX Services“.
Open Source to the Rescue!
Open Source Libraries and Frameworks to Support Enterprise 2.0 Apps, Widgets, & Gadgets
Creating Enterprise 2.0 Apps, Widgets, and Gadgets can be less time consuming with these free open source libraries and frameworks.
Google Web Toolkit (GWT)