Going Async - Practical Patterns for Push-Enabled Applications
summary
Hands-on recipe for a push service: use Vert.x embedded for event loops, SockJS to fall back from WebSockets, RabbitMQ for cross-instance pub/sub and Redis for session tracking. The demo builds a JSON handshake, creates Rabbit bindings per session, exposes an HTTP publish API, and routes messages to connected clients — messages arrive promptly on localhost. Mobile notes: watch battery impact, use native push (Urban Airship) as a claim‑check fallback.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 3:13Lets write some code
- 4:00Vertex
- 8:04Hello World
- 9:40WebSocket Handler
- 13:40WebSocket Client
- 16:43WebSocket vs SockJS
- 22:40SockJS vs WebSocket
- 25:30Building a Micro Protocol
- 29:07Session Manager
- 29:35JSON
- 31:22Event Bus
- 31:42Send Message
- 32:07Reply to Message
- 33:18Session Manager Overview
- 34:14Bindings
- 34:53Local Variable
- 37:21Remove Session Information
- 38:07Establish Session
- 38:30Session Response
- 38:59Rabbit bindings
- 40:37Create initial bindings
- 42:14Send messages
- 43:15Spring MVC
- 46:14REST Shell
- 46:33Rabbit
- 46:56Broadcast Binding
- 49:52Security
- 50:44Subscriptions
- 51:33Drawbacks
- 51:45Rabbit Exchange
- 53:17RabbitMQ
- 53:40New Topics
- 54:35New Subscriptions
- 55:06Rest Template
- 55:36Create New Subscription
- 58:37Whats Missing
related talks
36mPush it push it some more
45mGetting Pushy: Pushing Data From Server to Browser
58mService workers - beyond the cache
43mDesigning Event-driven architectures with AsyncAPI
43mRealtime Web Apps in the Wild
41mModel-View-Websockets
25mTaming Client-Server Communication
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging