The document discusses the importance of event-driven integrations within Salesforce's architecture, emphasizing the transition from point-to-point integrations to a more robust and decoupled model that enhances scalability and real-time integration. It highlights features like platform events and change data capture, which allow businesses to maintain consistency and react to changes in Salesforce data without complex coding or custom integrations. Additionally, it includes a disclaimer about forward-looking statements and potential risks associated with Salesforce's operations.

1. Event Driven Integrations
Dreamforce Global Gathering Bengaluru
Deepu Chacko, Technical Architect Director
https://www.linkedin.com/in/deepuchacko/
November 24, 2018
Salesforce Cloud Services India

2. 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.
Statement under the Private Securities Litigation Reform Act of 1995
Forward-Looking Statement

4. Agenda
• Why
• How
• Process – Platform Events
• Data – Change Data Capture
• Q & A

5. Why

6. Welcome to the Fourth
Industrial Revolution
We Are All Connected

7. Cost and complexity increases over time
Point-to-Point Integrations Slow Down Business
Year 1

8. Cost and complexity increases over time
Point-to-Point Integrations Slow Down Business
Year 3
Year 1

9. Cost and complexity increases over time
Point-to-Point Integrations Slow Down Business
Years 5+
Year 3
Year 1

10. How
Process – Platform Events

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

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

13. Platform Events Demo
Script
- Clicks: Publish & Subscribe
- Code: Publish & Subscribe
- Heroku External Subscriber

14. How
Data – Change Data Capture

15. Key Systems Need Up-To-Date Information
Businesses need to replicate changes in Salesforce to maintain consistency
Account {
Name : ”Acme"
}
Account {
?
}
Account {
?
}
insert acct = new
Account(Name='Acme’);
CRM Other Key Applications

16. Capture all record changes from your Salesforce org
Introducing Change Data Capture
No custom change-capture coding required
Easily select entities to capture data changes on with clicks
Capture granular data changes
Replicate Salesforce data to any downstream system
Real-time event-driven integration pattern
Decouple systems and scale without fear of breaking
“/data/ChangeEvents” Channel
Account {
Name : “Acme”
}
Account {
Name :
“Acme”
}
Account {
Name :
“Acme”
}
insert acct;
No polling
No batch ETL processes
No point-to-point integrations

17. Change Data Capture Architecture
Change Events
• Captured for data change events
• Published to change stream
• Sent to subscribed clients
Update Event
Account {
Name :
"Acme2"
}
Salesforce External System
Account {
Name:"Acme2"
}
Account {
Name:"Acme"
}
Update
Account {
Name:"Acme2"
}
Account {
Name:"Acme"
}
Enterprise Messaging
Platform Update

18. Change Data Capture Drives Key Use Cases
Master Data
Management
DATA REPLICATION
Update external
systems to reflect
changes in Salesforce
Back-Office
Integrations
PROCESS AUTOMATION
Downstream systems
react when Salesforce
data changes
Data Archival
AUDIT & COMPLIANCE
Changes in Salesforce
must be stored for an
extended period of time
Salesforce Event Bus
/closed_won
/new_account
/new_account
/data_change
Amazon S3
bucket

19. Orchestrate complex business processes without writing custom code
Easily Extend Platform Events with MuleSoft
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 data sources
Firewall
On-Prem 3rd Party Cloud
Salesforce Platform and
Change Data Event Streams

20. Change Data Capture Demo
Script
- Setup
- Workbench
- Mulesoft

21. Q&A

22. Salesforce Cloud Services team is growing and are hiring
Architects.
CLOUD & ENTERPRISE
ARCHITECTURE
● Business architecture models
● Multi-year plan Roadmap
● Process definition and optimization
DESIGN APPLICATIONS AT
SCALE
● Web and Cloud Hands on
● Heroku & Salesforce Integration
● Large scale deployments
MULTI CLOUD ARCHITECT
● Expertise and Specialization
● Multi cloud deployments
● Partner implementation advisor
Digital
Marketing
eCommerce
& Retail
CRM &
Sales
Strategy
Customer
Service
Excellence
Heroku
Architect
Enterprise
Architect
Technical
Architect