Pushing information is a decoupled and performance effective way to ensure interested parties have the most recent information ASAP.
This session looks at reasons and technology for pushing information at various points in an enterprise architecture. Databases can push to the middle tier, the middle tier pushes to the browser and mobile app - triggered by email, chat, JMS message or CEP event and one client can push to another. The link with Event Driven Architecture is explored.
HTTP Channels and Web Sockets are demonstrated as well as AJAX based background push, database query result change notification and HTTP calls from the database. We'll look at what to send in an event and how to present the push signal in the end user interface.
Attendees will learn how to effectively leverage concepts (such as Bayeux) and technologies to implement push-across-the-tiers in a scalable fashion- thus creating a modern application that satisfies the modern end user.
* Introduce push in the real world: don't call us and other examples
* Explain how push is good for performance (no polling), for decoupling (consumer does not need to know where the push comes from) and most up-to-date information available (as opposed to polling)
* Discuss architecture and all the gaps between and within tier where push may be required and how the trigger can originate
* Demonstrate how push can be implemented from a database to the middle tier (for example to refresh cache or send signal that ends up in client)
* Demonstrate how push can be implemented from middle tier to client - and what it can be used for
* Discussion of presentation/visualization of asynchronous, push-based refresh of client
* Leveraging the server-client push, demonstrate how client-client push can be implemented (through client-server AJAX and server-client push)
* Demonstrate end-to-end push: database undergoing some DML finally resulting in a browser being refreshed
* Linking Push with Event Driven Architecture and Complex Event Processing
* Brief future outlook