ISV Monthly Tech Enablement (August 2017)

1. ISV Monthly Technical
Enablement
August 2017

2. New Customers are Looking for Lightning Ready Apps
Lightning Ready = Your App Works in Lightning
Lightning Styling and Lightning Components are not required
New Apps Must be Lightning Ready to Enter Security Review
Make sure they find yours by being Lightning Ready
Learn More at: http://sfdc.co/LightningReady

3. Increased
Transparency
Coming Soon

4. Admins Want to Know What They are Installing
Coming Mid November
During Manual Package Install
Admins are warned about
Packages outside of
AppExchange Partner Program
Must acknowledge by clicking
checkbox

5. Admins want to know what’s in their Org
Coming Mid November
Admins can see Security Review status for installed managed packages

6. Why you Care, What you can do
The AppExchange and the Partner Program are built on Trust
Not all managed Packages are created equal
Admins want to know you’re in the Ohana
Make sure all of your Managed Packages are under contract and have passed Security Review

7. Platform Events
for ISVs
Enabling Real-Time Integration
Lynn Cohen
Technical Evangelist

8. Today’s Speaker Technical
Evangelist
Lynn Cohen
@slcohen

9. Forward-Looking Statements
​Statement under the Private Securities Litigation Reform Act of 1995:
​This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any
of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking
statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or
service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for
future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer
contracts or use of our services.
​The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our
service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth,
interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible
mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our
employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com
products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of
salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most
recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information
section of our Web site.
​Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not
be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

10. Agenda
▪ Why Platform Events?
▪ Use Cases
▪ Platform Events Demo
▪ Guidance
▪ Roadmap/Timeline
▪ Resources
▪ Q&A

11. Why Platform Events?

12. Typical IT system
integration
Customer Experience
IoT
Data
Science
Social
Mobile
Cloud
Point to Point Integration Slows Down
the Speed of Business
Trust &
Security
Customer
Data
Finding
Talent
User
Experience
Identity
Complex
Integrations
Open APIs

13. Integration is Real-Time with Platform Events
Real-time integration with
any business process
Create a full 360 degree customer experience
Event-driven workflows to
augment your data
Deliver real-time actions based on
both internal and external triggers
Capture and act on millions
of streaming events
Internal and external publishers and
subscribers.
Customers run business faster on an event-driven integration architecture

14. Real-Time Integration with Any Business Process
Apps communicate faster over
message bus architecture
Achieve agility and flexibility by decoupling apps, removing tight
dependencies and moving away from point to point integration.
Reliable flow of messages in and out of Salesforce
Time-ordered immutable event log enables systems to add
messages in order and replay events within a window of time,
increasing reliability and audit capability
Enterprise message bus architecture supports streaming events at scale
META DATA CRM DATA
INTELLIGENCE BIG OBJECTS

15. Introducing Platform Event Objects
Platform Events are first class objects in Salesforce
Developers define events in the same way as a custom object,
trigger and build workflows based on the event object
Publish/Subscribe from internal and external processes
Publish events through Salesforce API, Apex, and Process flows. External
apps subscribe to events via public APIs. Apex triggers subscribe on
platform.

16. App Cloud Message Bus
The Event Messaging Bus stores events
In time order
24 hour window
Events can be replayed
Multiple subscribers
Multi-tenancy support enforcing Org boundary

17. Use Cases

18. Sample Use Cases
Use Case Example
Update sObject data based on external
system state changes
Use standard APIs to publish events from
external order fulfilment system.
Real-time workflows kicked off by complex
business scenarios
Publish an event from Apex to represent an
"In-Danger Account".
Simplify inter-app integration Define Platform Events as an abstraction layer
representing state changes in underlying data
model, e.g. important milestones in a sales
process or activity on an Account that can
optionally create a Case.
Notify external systems of data changes Replicate data to Heroku for complex batch
processing.
Can implement with Platform Events now, but
Change Data Capture may be better fit when
available.

19. Demo

20. Demo
Node.js app publishes events
using REST API & subscribes via
open source nforce module
Lightning component subscribes
to event stream via CometD JS
library
Two Apex triggers:
● Platform event after insert
trigger creates Tasks for
subset of event sources
● Case trigger publishes
events for VIP accountsAccounts
Tasks
Platform Event
OpenAPIs
Apex Triggers
Special Handling for VIP
Accounts
Node.js App
Pub/Sub to Platform EventLightning Component
Source for demo:
https://github.com/lcohensf/platform-events-acct-alerts

21. Guidance

22. Platform Events Packaging
Packaged as a custom object
Professional and Group Editions are not
supported
In Apex unit tests, surround Platform Event
publication with
Test.startTest();
Test.stopTest();

23. Platform Events Limits
Description Performance and
Unlimited Editions
Enterprise
Edition
Developer Edition
Maximum number of events published per
hour
Events can be published using Apex or APIs.
100,000 100,000 1,000
Maximum number of events delivered to
CometD clients within a 24–hour period
50,000 25,000 10,000
Maximum number of platform event entities
that can be created in an org
100 50
5
(20 for Partner DE)
Concurrent Connected Clients
Shared with Streaming API
2000
Maximum event message size 5MB
Enterprise Scale Testing sandbox orgs are based on Enterprise
Edition.

24. 25k events
consumed/day
Provisioned to org;
Max of 5M
events/day
Event Consumption Limits
Enterprise Edition
(EE)
Need more?
100K additional
events1
consumed/day
Check with your
PAM to add to
your catalog.
ISV OEM
Add-on SKU
50k events
consumed/day
Provisioned to org;
Max of 5M
events/day
Unlimited Edition
(UE)
1
We do not count events consumed by Apex triggers.
Support for High volume customers (>5M events) is on the product roadmap

25. Limits Guidance
Other platform limits apply
API limits for publishing events
Each call to EventBus.publish() is a DML statement
Lightning Components or Visual Force pages subscribing via CometD are
treated as external consumers
Consider custom metadata to control generation of events from Apex
Plan ahead for event topic filtering in the design of your events
See Platform Events Developer Guide for additional considerations and
guidance.

26. Roadmap

27. Summer '17 (GA)
Platform Events
Apex Subscriber
External Pub/Sub Platform Events
Enterprise Messaging – Roadmap
Winter '18 (Dreamforce)
High Volume Events – Pilot
Change Data Capture - Pilot
Spring '18
High Volume Events – Beta
Topic Filtering
Enhanced Admin Functions

28. Resources

29. Where to Find More Information?
▪ Source for demo in this webinar - https://github.com/lcohensf/platform-events-acct-alerts
▪ Platform Events Developer Guide - http://bit.ly/Platform-Events-Summer-17
▪ Platform Events Trailhead Unit – http://bit.ly/Platform-Event-Module
▪ Platform Events Trailhead Project – http://bit.ly/Platform-Event-Project
▪ Platform Events Blog Post - http://bit.ly/Platform-Events-First-Impressions
▪ Chatter Group in Success Community – http://bit.ly/Platform-Events-Chatter-Group
▪ Change Data Capture TrailheaDX session - http://bit.ly/2ulIs9I

30. Q&A