This document discusses advanced event brokers, what they are, and when they should be used. It begins by describing the goals of early event brokers which focused on easy connections without libraries and using REST. It then discusses the additional capabilities of advanced event brokers, including resilience, monitoring, security, management, service discovery, and supporting multiple protocols. The document outlines how advanced event brokers can support hybrid cloud, IoT/digital transformation scenarios at massive scale. Key characteristics of advanced event brokers are described as smart routing/filtering, multi-protocol support, geographic awareness, security awareness, IoT optimization, and reliability. Examples use cases are provided such as connecting 10 million connected cars in real-time. In general, the document recommends using an

1. Advanced Event Brokers:
What are they, and when you
should use one?
Tom Fairbairn
June 5th 2018

2. In The Beginning
2
We wanted:
Easy connections
No libraries
REST!
• URI a service identifier
http://someserver/rest/endpoint

3. Resilience
load
load
HA
Proxy
Service inst 1
Service inst 2

4. The Merciless Mesh
oMonitoring
oAuditing
oFanout
oSecurity?
oManagement?
oSLA Monitoring?
oService discovery?

5. REST/API Gateway
Easier to add ”fanout”
Security
API
management
oHeavy weight – expensive to
scale
oRequest/Reply
oNo other protocols
Webhooks

6. Wait for it… synchronously
Request
Reply
Events!
Truly asynchronous:
oFailure tolerant
oFaster, more responsive UX
oDecoupling of applications

7. Back to microservices
• Polyglot persistence
• State and stateless tiered
architectures
• Event sourcing
“We have the algorithms to
save millions of lives, but
only if we dismantle data
silos” – Jeremy Howard,
CEO Enlitic
7

8. Along came the Event Broker
Event Broker
1
2
4 5
6
3
All
london.solace.com/AADI

9. But then… Remember this?
oLegacy -> Hybrid cloud
oHow to migrate? Piecemeal?

10. The Event Broker and cloud
Event Broker

11. And then this…
• IoT
• Massive scale
• Individual addressability
• Elastic: scale up edge tier

12. The Event Broker and IoT/Digital transformation
Event Broker
Browser
JS

13. What makes an Advanced Event Broker
Smart routing, smart filtering
• Route and filter data based on
receiving application needs
• Dynamic: based on application
requirements, not static config

14. What makes an Advanced Event Broker
Multi-protocol
• Don’t tell me how to do my job!
• Legacy integration
• IoT

15. What makes an Advanced Event Broker
Geographically/network aware
• WAN aware & optimised
• Disaster Recovery
• With routing and filtering over geographies

16. What makes an Advanced Event Broker
• Security aware
• TLS
• Role Based Access
• Dynamic/on-the-fly ACLs

17. What makes an Advanced Event Broker
• IoT optimised
• Bi-directional
• Delegated, hierarchical, elastic
addressing
• IoT Scale!
• 200k connections/instance
• 28M msgs/sec
• 80G b/w

18. What makes an Advanced Event Broker
• What gets forgotten
• In-service upgrades
• Open Source != Open Standards ->
Lock in
• Reliability & Robustness

19. Advanced Event Brokers in
action
19
USE CASES
You can drop an image here.
On this page, an image should never
be bigger than this box
10M Connected Cars, connected in
real time bi-directionally
A Leading German car manufacturer uses
Solace’s Advanced Event Broker to connect
10M connected cars to its entire event
processing, analytics & manufacturing
platforms

20. When to use an Advanced Event Broker
• Legacy & 3rd party apps
• Hybrid cloud
• Event driven, event sourcing
• IoT
• Security
• Simpler architecture
JMS MQ
Core/legacy
apps
Speak to us at booth S5!