MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events

December 14th 2021
Singapore MuleSoft Meetup #11

All contents © MuleSoft Inc.
Our Partners
2

Agenda
4
• 5:00 pm: Welcome & Introduction
• 5:10 pm: API Monetisation - Strategy and Approaches to Direct and
Indirect Monetisation
• 5:40 pm: Event Driven Architecture with Salesforce + MuleSoft
• 6:10 pm: Events roundup and quiz
• 6:30 pm: Meetup concludes

Co-host
6
Julian Douch – Senior Director
Capgemini
Integration veteran of 20 years, transformation strategist, and digital leader, established WhiteSky
Labs in ASEAN, and now leading the growth of MuleSoft adoption across JAPAC with Capgemini.
Passion for growing talent and dispersion of knowledge, I'm now driving fast to similarly establish
the MuleSoft community also, forging relationships with the current developer community,
expanding the community by reaching new technologists who've a passion for building out a new
API-centric digital economy.

Co-organizer / host
7
Royston Lobo
Senior Technical Architect
MuleSoft
Royston is part of the Customer Success Strategy and Architecture team at MuleSoft. He helps enable
MuleSoft customers to make the most of their MuleSoft experience through education, solving
problems and advising on strategic use of the platform.
Has the privilege of collaborating with customers, Professional Services, Product, Engineering,
Support, Marketing, Training and Sales teams to create value for MuleSoft and for our customers

API Monetisation -
Strategy and Approaches to Direct and Indirect Monetisation
Jason Cumberland + John D’Meric
HyperCurrent

Presenters
9
Jason Cumberland - CPO
HyperCurrent, U.S.
HyperCurrent’s software enables clients to maximize the value of their API ecosystem both internally and
externally. Our low-code platform empowers business owners to quickly create new B2B-focused
products & revenue streams through monetization of their customer-facing APIs. Similarly, HyperCurrent
provides CIOs the ability to meter internal API consumption, cross charge as needed, and correctly
allocate investment dollars to projects with the greatest usage & returns.
John D’Meric - Co-Founder / CTO
HyperCurrent, U.S.

© HyperCurrent, Inc. 2021
Unlock the value of your data and create new revenue streams with HyperCurrent
MuleSoft MeetUp
Dec, 2021

Agenda
● HyperCurrent introductions
● Relevance to MuleSoft clients
● Solution & architecture overview
● Product Demo
● Q&A

Why is Monetization Important?
● Data monetization is a quickly-growing trend as it opens new
revenue streams and staves off competition from newer
companies. It is a high-value conversation to introduce to your
companies or customers.
● Making MuleSoft the monetization hub ensures that all strategic
API initiatives are built around MuleSoft
● Adding monetization increases the value derived from ACM, which
extends into to a commerce platform with the addition of
HyperCurrent

Internal API
Productization
API Metering,
charge-back &
showback
External API
Monetization
New revenue streams
from proprietary data
Monetization of B2B
API ecosystems
HyperCurrent
HyperCurrent provides CIOs the ability to
promote API reuse through metering internal
API consumption, cross charge as needed, and
correctly allocate investment dollars to projects
with the greatest usage & returns.
Internally
HyperCurrent’s low-code platform empowers
business owners to quickly create new
B2B-focused products & revenue streams
through bundling & monetization of
customer-facing APIs.
Externally

External API Monetization

HyperCurrent
Digital Productization of
Disparate Data Sources
Digital Assets
List API Assets Available
for Productization
API Bundle 1
API Bundle 2
API Bundle 3
20
12
10
7.5
2
5
4.5
2
8
1
2.7
12
Desired
Product
Mix
Price, SLAs, & Entitlements
Define value; data or transaction
limits; response and/or
uptime performance
Credit Ratings
50
Product Mix
Combine assets into
new product
bundles
Risk Rating
Demographics
Credit Purchases
Loan Balances
Geolocation
Travel
Life Events
Search History
Bill Pay History
API Data Source Data
Value
Productized
Value
$100k / year, unlimited
calls, 99.9% uptime,
800ms response
$5k / month, 10k
calls / month, $0.75
per call overage, 99%
uptime
No commit, $1.50 / MB
transferred, $0.75 / MB
on weekends, 10 MB
free trial, no SLA
Entitlement &
SLA Governance
Accelerate product launches from months to minutes

7
HyperCurrent Architecture

8
HyperCurrent’s Commerce Engine Architecture

9
API Gateway Metering Integration
● Product Key: The Product Key is sent as a header by
the API Consumer for every API request.
● API Key: A unique key associated with every API
● Metering Policy: A HyperCurrent provided
Anypoint API Policy that asynchronously captures
API transaction metadata and reports to the
HyperCurrent Metering Beacon
● Metering Beacon: A sidecar that accepts data from
multiple metering policies and deterministically
rolls up API transaction data to the HyperCurrent
Transaction Engine

10
Productizing APIs with Salesforce, MuleSoft and
HyperCurrent: Reference Architecture
● Discovery and Experience
○ Prospects, existing Customers and
developers discover, learn and
engage with Productized APIs using
Anypoint Community Manager
● Fulfillment
○ Customers, either by working with a
sales rep or automatically via ACM
and/or CPQ API based products.
○ Subsequent API consumption (API
Keys, policies, etc) are provisioned by
the Anypoint Platform
● Metering and Chargeback / Monetization
○ HyperCurrent has 2 way
synchronization with Salesforce CPQ
and the Anypoint Platform to
synchronize products, monitoring and
API data
○ API usage is metered and billed by the
HyperCurrent Platform

Anypoint Community Manager Integration
● ACM Integration
○ HyperCurrent Lightning Web
Component installed as a Managed
Package (like ACM)
○ Re-uses pre-existing functionality from
HyperCurrent’s LWC UI/UX.
● Components
○ API Product Card
○ API Product Carousel
○ API Product Details Button
○ Create Notification
○ API Product Keys
○ Quotas
● Future Components (soon!)
○ Invoices

Contact Information
To get in touch with HyperCurrent, please contact Jason Cumberland,
(Jason@hypercurrent.io), or John D’Emic (john@hypercurrent.io).

Event Driven Architecture with Salesforce + MuleSoft
Ken Chang
Technical Architect, MuleSoft

Presenter
11
Ken Chang - Technical Architect
MuleSoft
Ken is a Technical Architect on MuleSoft's APAC Professional Services team. He works with
solution consultants and customers to solve enterprise integration challenges using an API-
led approach.

Enterprise Architects Are Faced with New Challenges
Drive business continuity through
integration
Handle data reconciliation when
integrating
Ensure secure data
access everywhere
Stand-up new, integrated
apps fast
Reopen businesses
with contextual data
Build real-time integration
architectures at scale
Expose key services as
reusable APIs
Integration
Architects
Migrate to cloud offerings
ASAP

Complex Integrations Power Connected Experiences
•Even simple services tend to have a lot happening under the hood
API Services
Web Services
Security
Services
Customer
Data
Driver
Data
Geo
Location
Data
Billing
Data
Data
Services

Data
Consolidation
Apps
Legacy Data
Multiple Orgs
API
Management
Proprietary
Data
But Integration Can be Challenging
IT navigates many systems and vendors to connect data
Devices
Custom
Integration

And become more complex over time
Point-to-Point Integrations Are Costly
Year 5+
A Headache
Year 3
5 Systems, 10 Integrations
Year 1
3 Systems, 3 Integrations

Run business faster on an event-driven architecture
Platform Events and Change Data Capture
Integrate in real-time across any business process
Create a seamless customer experience across systems
Augment data with event-driven workflows
Kick off downstream logic as soon as events take place
Keep external systems in sync when data changes
Capture change events and replicate them to any system
Invoke serverless Salesforce Functions
Event-driven access to elastic computing resources
GA 2021

{
Update_Status__e updateEvent =
new Update_Status__e(
Location__c='City’,
Urgent__c=true, );
}
Use a common language for workflows across internal and external systems
Events Are First-Class Objects in Salesforce
Define Events the same way as Custom Objects
Create Events with clicks in setup, then enrich with custom fields
Publish/Subscribe from internal/external web services
Publish using familiar APIs and Flow tools, subscribe with open clients
Support many different payloads for key workflows
Events can be defined as different types based on the data they carry

Move from point-to-point to a robust, decoupled model
Scale Integrations with an Event-Driven Architecture
Point-to-Point Event-Driven
Salesforce Event Bus

Publish events using programmatic or declarative tools
Easily Notify Key Systems of New Events
Subscribers
External Apps
Apex Flows APIs
Publish from Salesforce or external apps via API
Use Salesforce APIs to create and publish events programmatically
Trigger events from Salesforce with Apex
Create events and publish them with Apex methods
Produce events declaratively from your Flows
Use Lightning Flow or Process Builder to publish events with clicks

Respond to published events using a variety of methods
Enable Any System to Subscribe to Events
External Apps
Apex Flows
CometD
(Bayeux
Protocol)
Publishers
Consume events in Salesforce with Flows or Apex
Use clicks or code in Salesforce to subscribe to event streams
External apps respond via API and CometD
Easily deploy a CometD client for any external app
Extend events even further with middleware solutions
Leverage middleware like MuleSoft to extend Platform Events and Change
Data Capture events further

EventBus.publish {
“Closed Deal!”;
}
Publish Event
</Update Inventory> </Trigger Notification>
</Resolve Case>
</Create Invoice> </Update Report>
Drive robust process automation with an event-driven architecture
Real-Time Integration with Platform Events

Use Change Data Capture to keep external systems in sync with
Salesforce
Replicate Data Changes to Downstream Systems
Salesforce
Event Bus
On-Prem
3rd Party
Cloud
“ChangeEventHeader”: {
...
“entityName”: “Contact”,
“changeType”: “CREATE”,
...
}
Step 1: A contact is created
Data has changed in Salesforce,
and we’d like other systems to
reflect that change
Step 2: A change event is
automatically published
to a change event channel on the
event bus
Step 3: Subscribers consume the change
events
either directly with a CometD client, or
through middleware like MuleSoft
1 2 3

Replicate data without custom code
Easily select objects to capture data changes on with clicks
Keep your key systems up to date
Ensure downstream systems always have the right data
Create decoupled Salesforce apps and processes
Build scalable, asynchronous triggers on data changes
Scale with ease to millions of events daily
Events are held for 72-hours to allow replay as needed
Change Data Capture
Keep external systems in sync when data in Salesforce changes

Act faster with decoupled business logic for high-scale apps
Build Event-Driven Apps with Change Data Capture
/data/CaseChangeEvent
Change Data
Event
“ChangeEventHeader”: {
...
“entityName”: “Case”,
“changeType”: “CREATE”,
...
}
Lightning
empApi
CometD
Client
Subscribe from your
LWCs
Build event-driven
Flows
Create true async
Apex Triggers
Fan out changes via
MuleSoft
Keep external systems
in sync

Design Truly Async Apex Triggers
Complex computations and logic executed outside of the transaction
True Post-Commit Execution
Triggers execute asynchronously after a transaction
Faster End-User Experience
Less logic and computation inside the transaction leads to
quicker end-user experiences and fewer limit concerns
Event-Driven and Decoupled
Errors in processing won’t rollback or impact the transaction
trigger CaseChangeEventTrigger on CaseChangeEvent (after insert) {
// Setup
....
// Perform heavy computation asynchronously
....
// Cleanup / Finish
....
}
Get started fast with this open framework
for building Async Triggers

Where Platform Events Consume Limits
TRIGGERS
PROCESSES
Platform
Events
Lightning Page
(empApi)
REST API
SOAP API
BULK API
On Prem
HEROKU AWS EC2
+API limit
+delivered
+subscribers
+process subscribers
+published
+delivered
+subscriber
CDC
FLOWS
APEX
+published

+subscriber
+process subscriber
+process subscriber

+published
+delivered
+delivered
+published
Published Events:
Everything but CDC contributes to this number. Events
published through the API also count toward API limits
of the org.
With every High Volume Platform Event SKU, you
increase your maximum events published per hour by
25k.
Delivered Events:
Events delivered to CometD subscribers. Each delivered
notification counts toward this limit. If you have 10
subscribers and 5,000 events, the event delivery is 50,000
(process subscribers do not count).
(platform events) x (# subscribers) = delivered events
With every High Volume Platform Event SKU, you increase the
total delivered events by 100,000 each day. You also increase
your maximum events published per hour by 25k.
Once you buy at least one High Volume Platform Event SKU,
the delivery limit becomes a soft limit (you can exceed the
limit without Salesforce stopping delivery)

Orchestrate complex business processes without writing custom code
Easily Extend Change Data Capture with MuleSoft
Firewall
On-Prem 3rd Party Cloud
Salesforce Platform and
Change Data Event Streams
Capture Events with the Salesforce Connector
Pre-built connector for Change Data and Platform Events
Perform crucial data transformations
Allow for communication across protocols and data types
Deploy secure API gateways
Propagate events to on-prem and firewalled data sources

REST API + EDA = better together
REST APIs (push/pull) Event Driven (reactive)
Flexible & lightweight. Useson HTTP standard and is
format-agnostic. APIs are broadly supported on many
different types of clients: web, mobile, server-to-server.
Loose coupling. Producers and consumers have no
awareness of each other. Events are asynchronous.
Stateless & cacheable. REST APIs do not require server
sessions and resources can be cached on server or client.
Scalability. Producers and consumers can be scaled
independently.
Client-server decoupling. API clients and API server
communicate through a uniform interface. And the client
can only interact with the server in the indicated manner.
Fault tolerance. In case of a consumer failure, past events
are usually retained and can be consumed through a
“replay” mechanism.
Layered API architecture. APIs can be reused in a
composable manner to build new services.
Extensibility. Existing events can be used by new
consumers to implement brand new services.

When to use REST API / EDA
When to use REST APIs When to use EDA (Event Driven Architecture)
Synchronous request-response required. Asynchronous and loosely coupled workflows.
Unidirectional by nature.
Use case includes complex orchestration or
workflows.
Need reliable distribution of message to
multiple consumers – i.e. no message loss.
Need support for Strong Consistency. To handle longer running business
transactions through choreographies (rather
than orchestrations).
Organization requires governance and operational
control. The RESTful world has comprehensive
solutions & platforms for API lifecycle management
Schedule and forget jobs. Require scheduled
events to be eventually processed.

Salesforce Platform Event Replay ID
-1
(Default if no replay option is specified.)
Subscriber receives new events that are
broadcast after the client subscribes.
We recommend that clients subscribe with the -1 option to receive new event
messages. If clients need to get earlier event messages, they can use any other replay
option.
-2
Subscriber receives all events, including past
events that are within the retention window
and new events.
Catch up on missed events and retrieve all stored events, for example, after a
connection failure. Use this option sparingly. Subscribing with the -2 option when a
large number of event messages are stored can slow performance.

Event Driven API: Salesforce Platform Events
With Salesforce Platform Events, we can
either create
1. An Event Handler that subscribe to
Salesforce events and calls
relevant Process and System APIs.
Or
2. Process APIs that implement their
own Salesforce event subscribers.
We can also build an Event Sync API that
subscribes to Salesforce Platform Events,
then publishes the events to an on-
premise Kafka. This allows on-prem
systems to consume Salesforce triggered
events.

Event Driven API: Mobile App to Salesforce
At the experience layer, customer
interaction with mobile app triggers events
that are received by the Mobile API – via
Webhooks, pub/sub, etc. The event is
published to the Kafka Event Bus.
At the process layer, an Event Handler
subscribes to relevant mobile app events,
and invokes the appropriate Customer or
Order API as needed.
The system layer APIs provide access to
systems such as Salesforce and SAP.
Note 1: Event-driven workflows are
unidirectional in nature.
Note 2: APIs & Kafka can use intermediate
services to send push notifications to mobile
app.

Event Driven Architecture with MuleSoft

Learn how to build decoupled, scalable apps and integrations
Get Started with Event-Driven Architectures
Learn more about Salesforce eventing on Trailhead
Understand the basics of Platform Events and Change Data Capture with
three interactive trails
Take a deep dive into building and deploying events
Easily set up a CometD client or write Apex event triggers:
http://sforce.co/2DHfqBe
Dive into Change Data Capture on Trailhead!
Get started with syncing Salesforce to downstream
systems, then check out our dev guide for more!

Q&A
• Any questions?

WHAT TO EXPECT:
✔ Discover how the next evolution of API
management expands full lifecycle management
capabilities to APIs built and deployed anywhere —
this is a game-changer!
✔ Find the right solution to address your current IT
challenges, and see the future of automation,
composability, and integration.
✔ Get real-time answers to your most urgent API
questions during an “Ask Me Anything” session with
MuleSoft Product Managers.
Join us at the first-ever MuleSoft TRANSFORM and
discover how a clear API vision will help you
respond to changing market dynamics and address
critical IT challenges with speed, agility, and
efficiency.
WHEN
Thursday, December 9, 2021
1pm - 3:30pm AEDT / 10am - 12:30pm SGT
Now On Demand
https://www.mulesoft.com/transform/

Multiple IDPs for SSO
Highly requested feature from the
ideas portal
● Manage secure access to
Anypoint Platform using
multiple Identity Providers for
Single Sign-On
Connect to the platform using an IdP
of your choice
● Enable individual teams to use
an identity provider of their
choice to login
● Map groups of users
configured in external identity
provider into teams
Save time avoiding sprawling users
across different IdPs
● Migrate users from local
authentication or existing IdP
to another IdP easily
Available Now

The fastest and easiest way to connect apps and data for business
teams
Introducing: MuleSoft Composer
44
Connect apps and data instantly
Enable business teams to access data governed by IT using
clicks, not code — no more waiting for development
resources.
Take solutions from concept to
reality with ease
Allow business teams to jumpstart their own integration
projects using IT-built templates and to collaborate easily
with IT.
Scale integrations securely and
automatically
Empower IT to monitor every integration effectively,
without slowing down the business.

Same Connectors as Composer for Salesforce

Help documentation
published to
docs.mulesoft.com
5 mini-courses available at launch from
MuleSoft learning platform:
● Composer Basics
● User Management
● Google Sheets → Salesforce → Slack
● Workday → Microsoft Teams
● Stripe → NetSuite
Composer Community Forum
on help.mulesoft.com
Documentation Free Mini-Courses Community Forum
MuleSoft Composer Resources

New event
Higher Education group, Dec. 15
Local virtual events in +15 cities
Join from anywhere!
→ Join the Global Group: https://meetups.mulesoft.com/online-
group-english/
→ RSVP for upcoming events:
https://meetups.mulesoft.com/events/
+15 Virtual Community Meetups in December
48

50

What’s New & What’s Trending
Friends of Max
1.Secured connectivity to Salesforce using
OAuth JWT
2.Metrics Accelerator Installation Steps
3.Salesforce Integration with MuleSoft
Connectors
4.Custom Metrics and Custom Dashboards in
Anypoint Monitoring Demo
5.API Manager Overview - API Autodiscovery
vs. API Proxies
1.Deploy Mule app to CloudHub with GitHub actions
2.Simulating CloudHub 0.x vCore Workers in
Anypoint Studio
3.Real-time data with MuleSoft and Tableau
What’s new with Friends of Max? Top Videos in November

Questions
• 2 questions / brain teasers
• Write your answer in the chat window
• First correct answer(s) for each brain teaser will win a prize
• All winners will be contacted by email so please don’t forget to
provide registration name if you’ve joined via a different name

Question of the day
• Other than API monetisation, what other trend(s) do the
HyperCurrent team see being BIG in 2022?

Questions / Brainteasers
Skiing snowman
Which shadow
matches the
snowman?
1
2
3
4
5
6
7
8
9

See you next time
Please send topic suggestions to the organizer

MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events

MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events

Similar to MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events (20)

More from Julian Douch

More from Julian Douch (7)

Recently uploaded

Recently uploaded (20)

MuleSoft Meetup Singapore Dec 21 - API Monetisation with HyperCurrent & EDA with Salesforce Events