Click here to close now.


Microservices Expo Authors: Pat Romanski, Liz McMillan, Yeshim Deniz, Elizabeth White, Lori MacVittie

Related Topics: Agile Computing

Agile Computing: Article

Is Web 2.0 Possible with Existing Open Source Technologies?

AJAX Pushed

If you Google "AJAX Web 2.0" you'll get over eight million hits, but what technologies will you find in that mix that can truly deliver on the promises of Web 2.0 today? While there's no single definition of Web 2.0, at its heart lays the Internet acting as a platform for social networks, where information can be created and shared in a community of interest. Rich Internet Applications (RIAs) relate to Web 2.0 concepts only in that they enhance the platform by providing a more effective user interface. AJAX relates to Web 2.0 only in that it provides a lightweight approach for developing RIAs that execute through a single ubiquitous interface, the Web browser.

An examination of the interaction models for existing social networking platforms like wikis and blogs reveals that they lack the instantaneous nature of true human interaction. This is an artifact of the synchronous Web model that must be overcome when we consider next-generation platforms envisioned in the Web 2.0 spectrum. Internet-based chat is the most basic example of the near-instantaneous interaction that Web 2.0 demands, but even delivering these basic capabilities in a scalable, lightweight, browser-based mechanism is beyond the scope of most AJAX technologies. In fact, if you sift through those eight million Google hits, you'll find only a handful of open source technologies that address the problems associated with pushing content asynchronously to the user through standard browser mechanisms. We'll provide an overview of those technologies later, but first some basics.

The Basics of Web-based Push
Industry has not standardized on a mechanism or a name for asynchronous data push to the browser. In the AJAX realm the technique goes by a variety of names including AJAX Push, Comet, and Reverse AJAX, but regardless of what you call it, the various approaches share a common characteristic. The only lightweight communication mechanism available to the browser is the HTTP protocol, but HTTP only facilitates standard request/response communication initiated from the browser to the server. To deliver responses asynchronously, it's necessary to invert the HTTP protocol by holding an open request at the server, and fulfilling that request when an update is available. The differences between standard AJAX request processing and the inverted mechanism required for push are illustrated in Figure 1.

To support asynchronous push we need to hold a browser connection open in anticipation of a server-based event that will result in presentation changes in the browser. Intuition suggests that there are issues with this approach and in this case intuition serves us well, since we face connection-related problems at both the browser and the server.

Browser Connection Limit
One of the main difficulties faced by asynchronous Web techniques is caused by the typical browser "two-connection limit." To reduce server load, the HTTP specification recommends that user agents establish at most two connections per server, but asynchronous techniques consume one of these connections as a notification channel. Considering the case where multiple browser windows are open to the same Web page, if each window attempts to establish its own connection, we quickly saturate the available connections. To work within these limitations, a single connection must be shared, but the scripting environments of distinct browser windows are isolated for security reasons, making it difficult to coordinate a shared connection. One technique that can be applied is to make use of a shared HTTP cookie, which is associated with all HTTP interaction with a given server. The cookie is shared across windows and, by manipulation through JavaScript, can be used for cross-window communication.

The problem is amplified in portal environments because legacy portal engines don't support the necessary asynchronous communication path. For push to work in multiple portlets it's not only necessary to share the browser connection, but a single shared server connection is required to marshal asynchronous responses. If portlets are deployed from multiple WARs, there's an additional complication in that the sharing mechanism must coordinate between multiple Web applications and will require some IPC mechanism to do so.

More Stories By Ted Goddard

Ted Goddard is the senior architect of the ICEfaces AJAX framework. Following a Ph.D. in mathematics, he proceeded with postdoctoral research in component and Web-based collaborative technologies. He currently participates in the JavaServer Faces and Servlet expert groups.

More Stories By Steve Maryka

Stephen Maryka is CTO at ICEsoft Technologies Inc., and leads the ICEfaces open source project. He has been involved in Java-based AJAX techniques since 2003 - a time before the term "AJAX" was even coined. Prior to joining ICEsoft, Steve was co-founder of AudeSi Technologies where he served as VP of Technology and led Java product development for Internet appliances. After AudeSi was acquired by Wind River Systems in 2000, he served as a principle technologist there until joining ICEsoft.

Comments (2) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Most Recent Comments
radixweb 08/13/08 09:21:00 AM EDT

Hey, Great Post.. Thanks for this..

MiamiWebDesigner 08/02/08 09:34:25 AM EDT

Web 2.0 Is Like Pornography

Like so many tech articles posted since Tim O'Reilly coined the term in 2004, this one references "Web 2.0" as if it were something tangible--or at least a concept with clear, concise definition. It is not. In 2006, Web founder Sir Tim Berners-Lee sagely observed that "nobody knows what it means":

In 2007, Michael Wesch put together this video that supposedly "explains what Web 2.0 really is about":

It is a cool video. But the message is all about XML and how it can be used to separate form and content. There was no mention of CSS and XHTML, but no matter. I was writing XML parsers in the '90s, and XHTML/CSS web design pre-dates "Web 2.0" as well. No cigar, Professor Wesch.

And now in 2008, the most honest thing we can say is that "Web 2.0" means whatever the techno-marketeer (ab)using it wants it to mean. Otherwise, why would intelligent people like Isaac O'Bannon still be writing articles asking "What is Web 2.0?":

And, why would McKinsey's just-released best-of-breed report entitled "Building the Web 2.0 Enterprise" ...

... include no attempt at defining the term other than to list the "Web 2.0 Tools" that comprise or enable it? And even there, the chief ingredient is identified only as "Web Services", adding more mystery to the mix as one ethereal term is offered up to explain another.

As originated in an website design posting...

... "Web 2.0" is like pornography: Nobody has defined it, but you know it when you see it.

Bruce Arnold, Web Designer, Miami Florida

@MicroservicesExpo Stories
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how busine...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
IT data is typically silo'd by the various tools in place. Unifying all the log, metric and event data in one analytics platform stops finger pointing and provides the end-to-end correlation. Logs, metrics and custom event data can be joined to tell the holistic story of your software and operations. For example, users can correlate code deploys to system performance to application error codes.
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of