The document outlines details of a Solace user group meeting held on March 7, 2019, including the agenda with various case sharing sessions and a tech talk. It discusses challenges in event-driven integration and introduces the concept of an 'event mesh' to improve real-time event handling across hybrid environments. Additionally, it covers integration with microservices and cloud services to enhance application architecture and scalability.

1. Welcome to the
© S o la c e
P r o p r ie t a r y & C o n fid e n t ia l
HK User Group

2. HK User Group
Date: Thursday, March 7, 2019
Time: 4:00pm - 8:00pm (cocktail
reception at 6:45pm)
Location: R ONE Space, 26/F Sino
Plaza, 255-257 Gloucester Road,
Causeway Bay
AGENDA:
4:00pm Registration and Welcome Remarks
4:25pm Opening Remarks
4:30pm Case Sharing - OOCL & CargoSmart
5:00pm Case Sharing - NETS
5:30pm Case Sharing - Citibank
6:00pm Event Mesh Vision & Solace Tech Talk
6:30pm Audience Q&A
6:45pm Cocktail Reception
2
© Solace
Proprietary & Confidential

3. Enterprise Landscape is Changing
© Solace Proprietary &
Confidential
3
Simplicity
Agility
Cost
© Solace
Proprietary & Confidential
3
Containers
Hybrid Cloud Microservices
SaaS/
Opensource
Analytics/Insight
s

5. 5
© S o la c e | P r o p r ie ta r y & C o n fid e n tia l

6. Event Driven
Transformation
6
© Solace
Proprietary & Confidential

7. Example – Challenges of current integration
7
© 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

8. Event Enabled Price Change
Event Driven, API First Business Case
8
© 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

9. Event Distribution is Becoming More Complicated
9
© 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?

10. Event Distribution is Becoming More Complicated
10
© Solace
Proprietary & Confidential
Private Cloud/PaaSPublic Cloud
Capital Markets
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?
3. How do you scale, govern, make robust & secure?
Market
Data
Risk Settlements
Clearing
Analytics
Wealth
Managemen
t
Regulatory
Reporting
Reference
Data
Trading
FRTB
Development

11. © Solace
Proprietary & Confidential
11
The Answer is an Event Mesh
PaaSPublic Cloud iPaaS
Runtimes
• Uniform Connectivity
• Dynamic Routing
• Elastic Capacity
• High Performance
• No lock-in
• Security & Governance
Capital Markets
Market
Data
Risk
Settlements
ClearingAnalytics
Wealth
Management
Regulatory
Reporting
Reference
Data
Front officeTrading
FRTB

12. 4 Ways an Event Mesh Supports
your Application Architecture
12
© 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

13. How do the distributed event brokers work?
JMS MQ
API Gateway
Public Clouds PaaS
© Solace
13
© Solace
Proprietary & Confidential
13

14. Datacenter
Legacy
Public Clouds
JM S M Q
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
How does an event mesh work?
Dynamic Message Routing (DMR)
P Ca/b
a/b
Ca/b
C1
C2
C3
C a/b
P
c/d
C
c/d

15. Datacenter
Legacy
Private VPC
JM S M Q
New Apps
PaaS
Private Cloud Management - Single Pane of Glass
• Map view of
messaging services
• Easy launching of
PubSub+ Manager
• Easy DMR link creation
• Event Mesh insights
and visualization

16. 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
Com pressed Link
Norm al Link
Protocols
Connectors
JMS
JMS
C
JMS
iPaaS/Legacy
App

17. Demo Scenarios Outline
• Example US Based Bank
– Has Retail banking presence across US
– Looking leverage event mesh for global
market data distribution
– Uses public cloud for Western US
distribution
– Uses Private VPC deployment for Market
Data and Eastern
17
© Solace
Proprietary & Confidential

18. 18
© Solace
Proprietary & Confidential

19. Come on in,
the Solace cloud is fine!

20. What else?
• Replay
• Integration

21. Message Replay Protects Your Event Data
21
© Solace
Proprietary & Confidential
Publisher DatabaseSubscriberQueueReplay Log
1. Application publishes
event
2. Event added to
PubSub+ topic queue
AND to replay log
3. Replay continues to
store messages even
after they have been
delivered to all
subscribers
4. Subscriber can request
replay of delivered
messages at any time

22. Integration

23. 1. Cloud Native
Services
– From Solace cloud
Event Mesh - Ecosystem Integration
23
© Solace
LambdaEMR Kinesis
JMS MQ CDC
HybridEdge2.0
iPaaS
Kafka Cluster
Kafka Connect2
4
3
2. Legacy
Infrastructure
– Solace HybridEdge
3. Kafka Cluster
– Kafka Connector to
Solace Bridge
4. iPaaS
– Strategic partners
with several iPaaS
vendors
1
5
5. Platforms/
Runtimes

24. Making it Easy to Connect with Kafka
Kafka-compliant Source
and Sink Connectors
• In Solace Labs now
• Hybrid Cloud connectivity
• Large scale IoT deployments
24
© Solace

25. Native Application Integration - Spring
• Support for Spring boot,
Integration, Spring Cloud Stream
& Spring Cloud Dataflow
– Spring Cloud Stream: framework for
connecting scalable, event-driven
microservices to pluggable
messaging systems
– Spring Cloud DataFlow: cloud-native
orchestration service for
microservices
25
© Solace
Proprietary & Confidential
Spring Cloud StreamApp
Output
Channel
Transport Binder
Source
Spring Cloud StreamApp
Processor
Input
Channel
Output
Channel
Spring Cloud StreamApp
Sink
Input
Channel
Transport Binder Transport Binder
Event Broker – RabbitMQ, Kafka, or Solace

26. What’s next?
• Event Catalogue & Governance
• Async APIs
• AMQP/MQTT
• Private Cloud
• Streaming…

27. 27
© Solace
Proprietary & Confidential
dev.solace.com
cloud.solace.com

28. 28
© Solace
Proprietary & Confidential
Free Training

29. Developer
Educational
Brown
Bag
Inspirational
Experiences
Developer
Enablement
© Solace —
Confidential
Free Dev
Enablement

30. Demo Time
Hong Kong User Group

31. Demo Time!
• This is what we build during Dev
Enablement Sessions
• We go through all SOA to EDA
transformation patterns
© S o la c e
P r o p r ie t a r y & C o n fid e n t ia l

32. Building a boat race – traditional API centric
Player 1
Race display
Player 2
Player 3 …
Race application
How often should I poll ?
How do I synchronise the start / end ?
Is the user experience responsive?
Does it scale?

33. Building a boat race – the right way
Player 1
Player app
• Listen for race events race/UID/*
• Publish row(click) race/UID/PID/row
Race application &display
• Listen to clicks race/UID/*/row
• Publish positions race/UID/stats
• Start / stop/notify race/UID/[start|stop|etc]
And then
• Analytics
• Fan out to cloud
• Fraud/cheating/etc
Race application & display
Player 2 Player
‘to infinity and
beyond’

34. © S o la c e
P r o p r ie t a r y & C o n fid e n t ia l

35. © S o la c e
P r o p r ie t a r y & C o n fid e n t ia l

36. © S o la c e
P r o p r ie t a r y & C o n fid e n t ia l

37. That’s Possible
© Solace
Proprietary & Confidential
37