Advanced Event Brokers:
What are they, and when you
should use one?
Tom Fairbairn
June 5th 2018
In The Beginning
2
We wanted:
Easy connections
No libraries
REST!
• URI a service identifier
http://someserver/rest/endpoint
Resilience
load
load
HA
Proxy
Service inst 1
Service inst 2
The Merciless Mesh
oMonitoring
oAuditing
oFanout
oSecurity?
oManagement?
oSLA Monitoring?
oService discovery?
REST/API Gateway
Easier to add ”fanout”
Security
API
management
oHeavy weight – expensive to
scale
oRequest/Reply
oNo other protocols
Webhooks
Wait for it… synchronously
Request
Reply
Events!
Truly asynchronous:
oFailure tolerant
oFaster, more responsive UX
oDecoupling of applications
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
Along came the Event Broker
Event Broker
1
2
4 5
6
3
All
london.solace.com/AADI
But then… Remember this?
oLegacy -> Hybrid cloud
oHow to migrate? Piecemeal?
The Event Broker and cloud
Event Broker
And then this…
• IoT
• Massive scale
• Individual addressability
• Elastic: scale up edge tier
The Event Broker and IoT/Digital transformation
Event Broker
Browser
JS
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
What makes an Advanced Event Broker
Multi-protocol
• Don’t tell me how to do my job!
• Legacy integration
• IoT
What makes an Advanced Event Broker
Geographically/network aware
• WAN aware & optimised
• Disaster Recovery
• With routing and filtering over geographies
What makes an Advanced Event Broker
• Security aware
• TLS
• Role Based Access
• Dynamic/on-the-fly ACLs
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
What makes an Advanced Event Broker
• What gets forgotten
• In-service upgrades
• Open Source != Open Standards ->
Lock in
• Reliability & Robustness
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
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!

Advanced Event Brokers

  • 1.
    Advanced Event Brokers: Whatare they, and when you should use one? Tom Fairbairn June 5th 2018
  • 2.
    In The Beginning 2 Wewanted: Easy connections No libraries REST! • URI a service identifier http://someserver/rest/endpoint
  • 3.
  • 4.
  • 5.
    REST/API Gateway Easier toadd ”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 theEvent Broker Event Broker 1 2 4 5 6 3 All london.solace.com/AADI
  • 9.
    But then… Rememberthis? oLegacy -> Hybrid cloud oHow to migrate? Piecemeal?
  • 10.
    The Event Brokerand cloud Event Broker
  • 11.
    And then this… •IoT • Massive scale • Individual addressability • Elastic: scale up edge tier
  • 12.
    The Event Brokerand IoT/Digital transformation Event Broker Browser JS
  • 13.
    What makes anAdvanced 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 anAdvanced Event Broker Multi-protocol • Don’t tell me how to do my job! • Legacy integration • IoT
  • 15.
    What makes anAdvanced Event Broker Geographically/network aware • WAN aware & optimised • Disaster Recovery • With routing and filtering over geographies
  • 16.
    What makes anAdvanced Event Broker • Security aware • TLS • Role Based Access • Dynamic/on-the-fly ACLs
  • 17.
    What makes anAdvanced Event Broker • IoT optimised • Bi-directional • Delegated, hierarchical, elastic addressing • IoT Scale! • 200k connections/instance • 28M msgs/sec • 80G b/w
  • 18.
    What makes anAdvanced Event Broker • What gets forgotten • In-service upgrades • Open Source != Open Standards -> Lock in • Reliability & Robustness
  • 19.
    Advanced Event Brokersin 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 usean 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!