HTML and CSS Reference
Complex Event Process engines can also benefit from WebSocket architectures
by consuming, analyzing, and actively responding to events during the user's browser
session, a mobile device, or a thick desktop client application.
In a similar fashion, BPMS (Business Process Management Systems) would be able
to update the status of tasks that are part of large business processes executed throughout
the enterprise and show to the user in real-time what's happening with relevant parts of
The Web is clearly changing from a world of documents to a universe of activities
where live applications, not documents, flourish. WebSocket is a key component of this
new Web and will significantly transform how we use the Web in the enterprise and even
in our daily lives. The nature of the WebSocket provides the same kind of connectivity
that internal corporate clients already use to connect to the Enterprise Service Bus but
extending them to the Web.
A new and evolving set of capabilities, grouped together under the Web RTC
(Real Time Collaboration) umbrella with browser-based video and audio feeds are taking
us beyond real-time data on an even more exhilarating journey.
In this chapter we reviewed the concepts of messaging, an architectural style
characterized by sending asynchronous messages to build loosely coupled systems.
You learned about the pub/sub pattern, as well as STOMP, an open messaging protocol.
We explored an open-source STOMP and WebSocket-enabled message broker, Apache
ActiveMQ. After learning about simple configuration changes, we ran the ActiveMQ
STOMP-WebSocket demo, and then we built one on our own: rock-paper-scissors. Finally,
we reviewed the monitoring and management capabilities of Apache ActiveMQ.
In the next chapter, we will use RFB, the protocol used by VNC, on top of WebSocket
to build a real-time desktop sharing experience purely using HTML5.