Summit Puri, Global Head of Systems Engineering at Solace, talks about the architecture layer that will make your business event-driven. Find out more about event mesh in this presentation from Gartner AADI Mumbai on March 11th, 2019.

1. Event Mesh
The architecture layer that will make your
business event-driven
Gartner AADI, Mar 11, 2019
Sumeet Puri
Global Head of Systems Engineering, Solace

2. The Universe is
Event Driven

3. An Inventory Update

4. Sensors
firing

5. A Stock Price Tick

6. Heartbeat…

7. Modern enterprises are turning towards if not
fully embracing event driven architectures.

8. 2017
Gartner Says CIOs Must Define an Event-
Centric Digital Business Strategy
Press release: https://www.gartner.com/en/newsroom/press-releases/2017-07-10-gartner-says-cios-must-define-
an-event-centric-digital-business-strategy

9. 2018
“By 2022, event-sourced, real-time
situational awareness will be a required
characteristic for 70% of new digital
business solutions.”
Gartner: Top 10 Strategic Technology Trends for 2018: Event-Driven Model. 8. March 2018

10. 2018
“And 80% of new business
ecosystems will require support for
event processing”
Gartner: Top 10 Strategic Technology Trends for 2018: Event-Driven Model. 8. March 2018

11. Vision : Evolution from SOA to
Event Driven, API First, Cloud Native

12. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

13. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

14. Payment Order Prepaid
Recharge Order
An FX Order A Purchase
Order
An Order... is an order…is an order
And, an order is often an event!

15. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

16. T+3 settlement
High Value
Low Volume
SOA at best
Siloed amongst providers
Multi year projects
Payments – then vs now
16
Real Time
Low Value
High Volume
Event Driven
Fodder for AI/ML
API oriented
Agility needed –
implement QR Code in
weeks
2015 2020

17. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

18. Event Distribution is Becoming More Complicated
18
© Solace
Proprietary & Confidential
Private Cloud/PaaS
IoT
Public Cloud
Legacy Application Infrastructure
iPaaS
Runtimes
Yes, you can stitch it all together today…
1. How do you achieve “Uniform” connectivity and general event distribution?
2. How do you automate and federate across hybrid environments (low touch)?
3. How do you scale, govern, make robust & secure?

19. © Solace
Proprietary & Confidential
19
The Answer is an Event Mesh
PaaS
IoT
Public Cloud
Legacy Application Infrastructure
iPaaS
Runtimes
• Uniform Connectivity
• Dynamic Routing
• Elastic Capacity
• High Performance
• High Availability
• Security & Governance

20. Event mesh is an architectural layer that routes
events from producers to consumers in a flexible,
reliable and governed manner, no matter where
your apps are deployed.
Be Event Driven
API First
Cloud Native

21. What should you look for in an event broker?
Dynamic: self-routing, self-learning, self-healing.
Open: protocols & APIs.
Simple: deployment, governance, scalability.

22. Event Driven - Advanced Event Brokers and Event Mesh, REST & beyond
Distributed Event Brokers
Smart Routing
Edge Fanout
Guaranteed Delivery
Network Optimization
Pub Sub | Streaming
Filtering | Queuing
Adapters | Connectors
Replay
Public Cloud
Private Cloud
PaaS
Hybrid Cloud
REST
AMQP
JMS
MQTT
WebSockets
Connectors
Zero downtime
Zero data loss
Governance
Security
Burst Handling
High Performance

23. Who is Solace?
World’s foremost experts on event
distribution and messaging
middleware
- 21 patents
- 9 of top 12 Investment banks
- Top American & Indian telcos
- Air traffic management around the world
HQ and Manufacturing
in Ottawa, Canada
15 Global Offices
Presence in Asia &
China, Europe, US,
Australia
23
Award-
winning
business

24. The Un-named Event Mesh – Trading platforms
THE SOLACE HERITAGE
18μs latency 99.999% uptime 28M msg/sec
Pub/Sub & Queuing Zero Data Loss Multi Protocol
WAN Optimization Burst Handling Hybrid Cloud
Often replaced TIBCO
EMS, RV, Kafka, IBM
MQ, RabbitMQ,
ActiveMQ, ZeroMQ,
Kaazing, WebMethods,
SoftwareAG UMS, 29W…
And
many
more!

25. 25
© Solace
Proprietary & Confidential
solace.com
cloud.solace.com
Appliance

26. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

27. Example – Challenges of current integration
27
© Solace
Proprietary & Confidential
Price
Change
EVENT
ESB
API
Expose
Price API
GetPrice
Request Reply
API
• Price change is an EVENT
• Not Pushed - But it is exposed as a Request
Reply API – which is required
• Non Real Time - Downstream applications do
not get to know that the Price has changed,
until they ASK – Request Reply API
• Bursty - Event application calls the API – which
causes load/burst – expensive to scale
• An “async” API would be better for events than
“sync” APIs
GetPrice
Request Reply
API
GetPrice
Request Reply
API

28. Event Enabled Price Change
Event Driven, API First Business Case
28
© Solace
Proprietary & Confidential
Price
Change
EVENT
ESB
API
Expose
Price EVENT
API
Subscribe for
Price Update
EVENT
• Price change is an EVENT
• Pushed - But it is exposed as a Request Reply
API – which is required
• Real Time – interested downstream apps
subscribe to events of interest. When event
happens, Event Mesh pushes it to interested
applications
• Burst Handling – Event Mesh “Queues” and
”Throttles” events during burst
• Cost Effective to Scale – scale for average,
rather than peak
• An “async” API would be better for events than
“sync” APIs
Subscribe for
Price Update
EVENT
Subscribe for
Price Update
EVENT
Publish Event to the
Event Mesh
Also exposed Request
Reply APIs

29. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

30. Digital 1.0 - SOA and it’s challenges
30
© Solace
Proprietary & Confidential
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 challenges
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!
Burst=
Bottleneck

31. Event Routing – the power of topics and wildcards
* > & +
Events have Topics:
ord/conf/v1/printer/inkj/m1234
REST URL = Topic:
https://host:port:/ord/conf/v1/printer
/inkj/m1234
Events have payload:
Binary | JSON| XML |
Images |Anything
Events can be subscribed:
Wildcards:
ord/> - all orders All orders
ord/*/v1/> all orders of version 1
ord/conf/v1/printer/in
kj/>
all order confirmations for
inkjet printers

32. Microservices consume and produce events
ord/conf/v1/printer/inkj/m1234ord/v1/printer/>
Validate Order and Issue Confirmation
Microservices
Microservices process fine grained business logic
Microservices consume and produce events

33. Must Be Sync - Serial
Responsive Apps - Eventual Consistence, Deferred Execution
Can Be Async – Parallel
Eventual Consistency
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

34. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

35. Must Be Sync - Serial
Event Driven and Request Reply APIs
A PAYMENTS EXAMPLE
Can Be Async – Parallel
Eventual Consistency
Expose functionality via Sync and Async APIs
Order Status Polling
vs Order Status Notification
Multi Protocol
APIs
Micro Gateway
REST
WebSockets
MQTT
AMQP
Validate
Payment
Funding
Check
Risk and
Queries
Clearing &
Settlement
DWH,
Tracing,
Audit
API GW

36. Similarities of API Management and Event Management
(Solace view)
Source: Gartner Application Strategies & Solution Summit Presentation “Governing
Next-Generation API Infrastructure”, Mark O’Neill, 27-29 November 2018

37. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

38. Hybrid
Cloud
38
AI/ML

39. Must Be Sync - Serial
Hybrid Cloud – AI, ML and Microservices
Can Be Async – Parallel
Eventual Consistency
Event mesh extends to all clouds
Events Seamlessly flow
Multi Protocol
APIs
Micro Gateway
REST
WebSockets
MQTT
AMQP
API GW

40. Datacenter
Legacy
Public Clouds
JMS MQ
New Apps
PaaS
• Use DMR to horizontal scale
cluster
• Use DMR for hybrid cloud
dynamic routing
• Source based filtering & WAN
optimization
• Persistence and non-persistence
Hybrid Multi Cloud Event Routing
Dynamic Message Routing (DMR)
P Ca/b
a/b
Ca/b
C1
C2
C3
C a/b
P
c/d
C
c/d

41. Solace
Solace
Solace
Solace
SolaceSolace
SAP Cloud
Datacenters
… and Helps all SAP Customers to Stay Connected
SAP Customer
Solace interconnects the SAP Cloud

42. 1. Start thinking events
and not just data
2. Identify Candidates for Real
Time
why not real time?
3. Get going with the Event Mesh
Event Brokers, Event Catalogue, Event Routing
4. Select Pilot Event Flows
Being Event Driven
RECIPE TO
5. Decompose into Micro-
Services
Serial, Parallel - Async
Eventual Consistency
Deferred Execution
6. API First
Async APIs
7. Go Cloud Native
Hybrid Cloud
Multi Cloud
8. Rinse and Repeat

43. 4 Ways an Event Mesh Supports
your Application Architecture
43
© Solace
Proprietary & Confidential
Connecting
and Orchestrating
Microservices
Event
Mesh
Pushing Events
from On-Premises
to Cloud Services & apps
Event
Mesh
Enabling Digital
Transformation
for IoT
Application Tier
Event
Mesh
Enabling Across
LoBs DataaaS

44. IP Network
Layer
Event Mesh
Federal Application and Services Layer
Solace Event Mesh – Connecting across networks
Agency | Market Data | Factory Floor
Public Cloud
Private Cloud | Colo | Suppliers
Applications
Dynamic pub/sub to
other clouds
Non Latency
Sensitive apps
Public Cloud
Non Latency
Sensitive apps Analytics
Encrypted Link
Compressed Link
Normal Link
Protocols
Connectors
JMS
JMS
C
JMS
iPaaS/Legacy
App

45. Be Event
Driven
© Solace
Proprietary & Confidential
45
Sumeet Puri – Global Head of Systems
Engineering
sumeet.puri@solace.com
Visit us at booth #S1
Thank You
API First Cloud Native