The Event Mesh: real-time, event-driven, responsive APIs and beyond

The Event Mesh
Real time, event driven responsive APIs and beyond
Phil Scanlon

AGENDA
Introduction
Evolution to
Event Driven
The anatomy of
an Event
Wrap-up
Real World
examples
Demo

You might not know our name, but…

Who is Solace?
World’s foremost experts
on event distribution and
messaging middleware
‐ 250+ employees
‐ 100+ in R&D
‐ 100% focused
‐ 24 patents
HQ and Manufacturing
in Ottawa, Canada
15 Global Offices
© Solace
Proprietary & Confidential
4
Award-
winning
business
Award-
winning
business
Proven, Trusted
• 9 of top 12 Banks
• Top American and Indian telcos
• Air traffic management around the world
• Top auto makers for connected car initiatives
• Singapore smart city and transportation
• One of top phone manufacturers

Evolution to events
5
© Solace

In the beginning…
• Companies ran their own
datacentres
– Huge investment in hardware,
maintenance, support, and expertise
– VMs, virtualization, and
containerization allowed more
efficient use of hardware
– Wouldn’t it be nice if someone else
could manage all the hardware,
storage, networking?
– The birth of IaaS, and PaaS

In the beginning…
• Software was monolithic
– Database-centric, batch-oriented systems
– Proprietary protocols and APIs
– Concept of ESB to help integration and
orchestration of services (SOA)
– Rise of open-source, open standards,
open protocols, and open APIs
– Decomposing of larger systems into
collections of microservices
– Move to real-time, increase In volume,
rethinking to Event-Driven Architectures

In the beginning…
• The Internet was simple
– Client-Server interactions for webpages
– RESTful Request-Reply HTTP protocol
– Everything understands REST: firewalls,
routers, gateways, load balancers, etc.
– But also synchronous; but also one-way
– Need for efficient, asynchronous,
bidirectional protocols
• WebSockets, MQTT, etc.

In the beginning…
• “Things” were dumb
– Telephones, cars, lights,
refrigerators, houses, browsers,
devices of all sorts
– Massive improvements in
miniaturized computing power
and network access promoted
connectivity
– Growth continues, with 28B
devices by 2021

Digital 1.0 - SOA and it’s challenges
API GW
Validations
Fraud Check
Credit Check
Core Banking
Systems of
Records
Tracing
Audit Logging
Ops
Clearing GWs
SWIFT GW
Other GWs
Compliance
Reg Reporting
Risk
SOAP/HTTP
SOAP MQ MQ JMS Adapter
Lets look at a Payments
scenario, others are similar
Traditional SOA
Characteristics
• Request Reply
• Orchestrated Flow
• Serial
• SOAP, changing to REST
Channels
ESB

Digital 1.0 - SOA and it’s challenges
API GW
ESB
Validations
Fraud Check
Credit Check
Core Banking
Systems of
Records
Tracing
Audit Logging
Ops
Clearing GWs
SWIFT GW
Other GWs
Compliance
Reg Reporting
Risk
SOAP/HTTP
SOAP MQ MQ JMS Adapter
Challenges:
• Orchestrator is a bottleneck
• Serial = slow response time
• Slow time to market
• Difficult to leverage AI/ML –
requires big changes
• Cloud adoption
Channels
Cloud Native
Storage
Cloud Native
Services
AI ML
New Services
?
?
Slow causes
response time
impact, errors
Response time is a
summation of all services!

REST isn’t Always Best
Great for:
• Synchronous interactions
• Externally facing APIs
But:
• Point-to-point
• Tight service coupling
• Not natively event-driven
• Polling

Quest for agility is driving you to the cloud,
to microservices, to EDA, to new tools…
ExecutivesExecutives
Digital Ambition
• Transform?
• Optimize?
Cloud Opportunity
• Cloud de jour?
• Paas?
Accelerate Innovation
• Continuous intelligence
• Combine data/event silos: IoT,
ML/AI, Legacy Systems, etc.
ArchitectsArchitects
Digital Optimization
• Legacy systems
• iPaaS vs. API Gateway?
• Microservices?
Cloud Necessary
• Churn: target cloud
keeps changing
• Which PaaS?
• Hybrid reality
Innovate…
• Events not data
• Leverage ML/AI
• Big data + IoT Sensors +
Mobile
DevelopersDevelopers
Sounds Great!
• How do I integrate to
get access to data?
• Springboot for microservices?
Cloud Native
• Lambda?
• Containers?
• CI/CD and Infra as code
Innovate!
• Streaming
• Event sourcing
• Spark
• I only know about MY silo’s
API and data definitions

How do you enable event‐driven interactions across all this stuff?How do you enable event‐driven interactions across all this stuff?
Making the distribution of data more complicated
Legacy Applications IoT
Legacy Application Infrastructure
Cloud
Private Public
iPaaS / APIsiPaaS / APIs SaaSSaaS

“A key distinction of a
digital business is that
it's always sensing and
always ready, which
demands grounding in
event processing.”
Source: Gartner
Business Events, Business Moments
and Event Thinking in Digital Business.
4 August 2017
Shift to Event-Driven Architectures and Thinking
15
Lives, businesses are event-driven…
– Mouse click, a screen tap indicates user action
– Temperature sensor detects threshold exceeded
– A command and control call to stop a machine
– A Master Data Update Event, a plane taking off
– Even an API call…
Our lives, the universe, are event-driven…
So why is
computing
usually Request
Reply?

Gartner: Top 10 Strategic Technology Trends for 2018:
Event-Driven Model. 8 March 2018
Shift to Events
is Accelerating
Event-driven microservices are
the optimal software design
model to delivery digital
business agility.
By 2022, 70% of new
digital business solutions
will require event-sourced,
real-time situational
awareness.

Don’t use Y2K
techniques to
deal with 2018
realities
How do you support the shift to “event-driven”?

Event Distribution is Becoming More Complicated
PaaS
IoT
Public Cloud
iPaaS
Runtimes
Yes, you can stitch it all together today…
But how do you
uniformly connect the
old world with the new?
How do you ensure
high availability, maximum
security and smart governance?
How do you make
your infrastructure
fast and easy to scale?
And how do you automate
for self-learning, dynamic
low-touch operation?

The Answer is an Event Mesh
© Solace
PaaS
IoT
Public Cloud
iPaaS
Runtimes
• Uniform Connectivity
• Dynamic Routing
• Elastic Capacity
• High Performance
• High Availability
• Security & Governance
GB1

GB1 Greg Barr, 17/08/2018

Why Messaging?
• Supports standard, open,
event-driven APIs
• Native pub/sub
and ordering
• Supports request/reply
Eventing Requires Messaging & Streaming
Why Streaming?
• Replay
• Native pub/sub
and ordering

Any API/Protocol
AMQP, JMS, MQTT, REST, etc.
Any Deployment Model
Software, As-a-Service, Appliance
Any Environment
Cloud, On-Premises, Hybrid
Any Quality of Service
Guaranteed, best-effort, etc.
The event-broker powering the
Event Mesh that supports
publish/subscribe plus:
– Queueing
– Request/Reply
– Streaming
With common deployment,
APIs and administration
© Solace
21

Message Exchange Patterns
StreamingRequest/Reply Publish/Subscribe

Think Event Driven Microservices
–Microservices have inputs and outputs
• Inputs and outputs can be thought of as “events”
–So what is an Event?
• An event is an action or occurrence recognized by software, often originating
asynchronously from the external environment, that may be handled by the software
–Stop thinking about services INVOKING services!
• Instead services emit events!
–What/where do we emit these events to?
• Messaging (preferability Solace!)

Event Mesh
Event
Mesh
Event
Mesh
3 Ways an Event Mesh Improve your Infrastructure
Connecting
and Orchestrating
Microservices
Pushing Events
from On-Premises
to Cloud Services
Enabling Digital
Transformation
Across LoBs and IoT

Parallel ‐ Can Be AsyncMust Be Sync ‐ Serial
Event Mesh – APIs, Event Routing and Response Time
25
© Solace
API GW
SOAP/HTTP
Characteristics:
• Every flow has some serial and some
parallel paths
• Only serial path should influence
response time
• Event Mesh routes messages via
PubSub, including wildcards
• Lossless Streaming and Queuing
both supported – must have for
parallel path
• No orchestration needed,
choreography
Channels
Validations
Fraud Check
Credit Check
REST
1
Core Banking
Systems of
Records
MQ
Adapter
JMS
2
Clearing GWs
SWIFT GW
Other GWs
MQ
Adapter
JMS
3
Tracing
Audit Logging
Ops
JMS
4
Compliance
Reg Reporting
Risk
AMQP
4
No impact on
response time!

Event Mesh – Lossless, Parallel Streaming
26
© Solace
API GW
SOAP/HTTP
• Event Streaming
among micro
services
• Pub Sub
• Lossless
Channels
Validations
Fraud Check
Credit Check
REST
1
Core Banking
Systems of
Records
MQ
Adapter
JMS
2
Clearing GWs
SWIFT GW
Other GWs
MQ
Adapter
JMS
3
Tracing
Audit Logging
Ops
JMS
4
Compliance
Reg Reporting
Risk
AMQP
4
No impact on
response time!
Fast Response
Slow causes no
impact!

Event Mesh – Agility, Insights and Hybrid Cloud
27
© Solace
API GW
SOAP/HTTP
Characteristics:
• Plug and play for new microservices,
insights etc – no other
ESB/Microservice change
• Lossless Hybrid Cloud events
Channels
Validations
Fraud Check
Credit Check
REST
1
Core Banking
Systems of
Records
MQ
Adapter
JMS
2
Clearing GWs
SWIFT GW
Other GWs
MQ
Adapter
JMS
3
Tracing
Audit Logging
Ops
JMS
4
Compliance
Reg Reporting
Risk
AMQP
4
No impact on
response time!
AI ML
Flink

Event Mesh – Agility, Insights and Hybrid Cloud
28
© Solace
API GW
SOAP/HTTP
Characteristics:
• Event Catalogue is used to Design
and Runtime Governance
• ACLs Enforced, and and Stats are
retrieved
• Data Lineage
Channels
Validations
Fraud Check
Credit Check
REST
1
Core Banking
Systems of
Records
MQ
Adapter
JMS
2
Clearing GWs
SWIFT GW
Other GWs
MQ
Adapter
JMS
3
Tracing
Audit Logging
Ops
JMS
4
Compliance
Reg Reporting
Risk
AMQP
4
No impact on
response time!
AI ML
Flink
Event
Catalogue
Replay
Event
Sourcing

Applications of an Event Mesh
IoT
• Device connectivity
• Event routing & distribution
• Protocol rationalization
Modern Messaging
• Hybrid/Multi-cloud bridging
• Connecting new and old world
• Application Integration
Enterprise Integration
• Local connection of apps and data
• Strategic enterprise-scale
digital transformation
Microservices
• Synchronous and Asynchronous
• Service mesh overlay to
enable publish/subscribe
© Solace
29

• One platform for
Command, Query and
Event
• Unification of REST APIs
and event-driven APIs
• Cloud native messaging
enables developer
agility
• Decoupling of services
for dynamic process
flow
Event Distribution in Microservices Environments
31
© Solace
Event Broker
Mainframe
Systems
of Record
Distributed
Apps
Legacy
Messaging
Microservice
Event Driven Apps
Internet of Things
Mobile / B2B
Event Broker
API GatewayAPI Gateway
Internal
Audiences
Partners Customers
Event Broker

On-Premises SystemsOn-Premises Systems
• Unify events across
clouds and on-prem
• Freely share data and
workloads across
multiple clouds
• Flexibility as market
unfolds
• Open source
connectivity with legacy
technologies
Event Distribution Across Hybrid & Multi Cloud
MessagingMessaging MainframeMainframe
Public Public
© Solace
32

• Seamless data flow
across devices and
applications
• End-to-end
addressability enables
ingestion and command
& control
• Protocol support and
transformation
• Massive scale with
built-in filtering and
burst handling
Event Distribution in the Internet of Things
AMQP
Applications in Cloud
and Datacenter
Sensors, Vehicles
and Control Systems
JMS
MQTT
REST
MQ
?
© Solace
33
Hybrid/Multi-Cloud
Event Routing
Any Protocol, Any Pattern
Legacy Integration Framework
Event Management
Security

Solace Digital Case Study: NETS Group
• The NETS Group enable digital payments for
merchants, consumers and banks across the entire
payments value chain.
• 102,000 terminal’s accepting QR Codes
• Solace’s Event Broker allows NETS to reliably and
securely route the real-time information involved
with large numbers of transactions
“Without Solace we
were unable to rollout
our technology fast
enough. We can now
onboard a bank a
month. Previously it
took 3 months” Vincent Low
CIO NETS

NETS Singapore Payments
Messaging as a Digital Backbone
JSON/REST
or JMS/MQTT
Legacy
Gateway
REST message: URL for event routing
http://mybank/pay/merchId/cardpr/type/xyz/xyz
Data In Motion
Complex Events
Processing
Fraud Detection
JMSTopic:
mybank/pay/>
Visual
Analytics
(Splunk)
JMSTopictoQueue:
mybank/POS/Monitor/
>
LosslessQ
ShockAbsorber
Solace
Data At Rest
Analytics
(Hadoop)
JMSTopic:
mybank/>
Lossless Q
Shock Absorber
Topic to Q mapping
Payment
Switch
Payment
Switch
Connectivity
Data Store
Cache
ESB/Transform
ESB/Transform
JMS Topic:
mybank/pay/*/cardpr/>
mybank/pay/*/cnp/>
Wildcard routing on
REST URLs/Topics
Filtering and Topic
(subject) Routing with
Wildcards
Persistence – never
lose a message
Publish Subscribe -
Parallel, Async
Processing
Multi Protocol
REST <> JMS <>AMQP <>
MQTT
Burst Handling and
Throttling – Big Data
Ingest
Lambda Architecture –
Speed and Batch

36
Copyright Solace
Confidential
FAA
• Solace fans out National Airspace
System SWIM data feeds to
airlines, airports, FlightAware, etc.
• Traffic Flow/ Flight Plans STDDS
– Collect/publish data from 150+ airports,
SFPDS , TBFM, TFDM
• Why Solace?
– Predictable, high
performance
– High fanout for large
number of connected
systems over WANs
– Fast fail over time to
support business continuity
– Easy to manage with more
real-time monitoring and
response
– Built-in hardware
compression reduce WAN
bandwidth
© Solace
36

Solace IoT Case Study: Core Transport Technologies
• Core TT provide logistics solutions to Airlines, Cargo carriers and US
government agencies.
• Solace is the event backbone for CORE's worldwide IoT implementation
• Solace Event Brokers are deployed both in the Cloud and on Premise to
manage all the logistic events
• Solace effectively synchronizes and exchanges critical information in real-time,
updating users on the status of their deliveries as well as potential logistical
problems
“Solace gives us the
ability to dynamically
manage and deliver
information in real time
which is critical to
maintaining contingency
plans and adapting as
events unfold. This
enables quick, informed
shipping decisions,
keeping services efficient
and effective.”
© Solace
37
Ian Craig
Managing Director
Core Transport Technologies

Solace Cloud Case Study: VoiceBase
• VoiceBase provide automatic speech-to-text, speech analytics and
predictive insights, powering intelligence every business needs.
• VoiceBase uses Solace messaging technology to intelligently route
voice, video and text events through their system.
• Solace Event Broker acts as a shock absorber during peak times
and allows VoiceBase to scale out on demand
“Only one
enterprise service
bus worked, and it
didn’t even break
a sweat"
© Solace
38
Jeff Shukis
VP Engineering
VoiceBase

The Event Mesh: real-time, event-driven, responsive APIs and beyond

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a The Event Mesh: real-time, event-driven, responsive APIs and beyond

Semelhante a The Event Mesh: real-time, event-driven, responsive APIs and beyond (20)

Mais de Solace

Mais de Solace (20)

Último

Último (20)

The Event Mesh: real-time, event-driven, responsive APIs and beyond