Safe Harbor
Safe harbor 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.
Multi-Tenancy Greatly Expands Enterprise Cloud Capabilities
Force.com APIs
Salesforce1 Mobile App
Force.com Platform
Sales
Cloud
Service
Cloud
Custom
AppApp
Exchange
Multi-tenant Infrastructure
Multi-Tenant
Infrastructure
Core Tenets of Infrastructure
Application
Innovation
Performance
at ScaleAlways On
AvailabilityTrusted
Security
Salesforce Security Provides Multi-layer Zones of TrustAdaptive Flexible Security Model
Infrastructure-level SecurityApplication-level Security
Firewall SSL
Accelerators
Web/App
Servers
Load
BalancersDatabase
Servers
Trusted
NetworksAuthentication
Options
Field Level
Security
Object
Level
Security
(CRUD)
Audit Trail
Object History
Tracking
Overall site peak day
• >2 Billion transactions
• 200 milliseconds average
• 60% of transactions via API requests
Typically production instance
• >8,000 Customer Orgs
• 30 App Servers and 8 DB Servers
Salesforce.com’s Daily Performance
Yesterday - ~2.5 Billion Transactions
3 Releases Per YearAPI backward compatibility ensures ease of deployment
45 Major Releases
100’s of Small Releases Yearly
All Integrations and
Customizations Auto-Upgraded
6BLines of
Apex Code
1BAPI CallsPer Day,
32 versions
12MVisualforce
Pages
15MCustom
DatabaseTables
1Version
One Cloud with Many Customers
Environment = Tenant = Organization or “Org”
• One Primary Data Store per
Production Instance
• All data segregated by customer
• All operations include Org ID
• Multi Author
A single slot can store various types of data that originate from different objects
Data Id Org Id Object Id Name Field0 Field1 …
a01dI000000qKJi 00D01… a01 A0001 Red 20141024
a01dI000000qKJj 00D01… a01 A0002 Blue 20131023
a02dl000000prNy 00D01… a02 Fiat 12000.00 true
a02dl000000prNz 00D01… a02 Ford 15000.00 false
a01dl000000cKSr 00D02… a01 Eiffel Tower ½ Day Paris
a01dl000000cKSr 00D02… a01 Historic Slough 1 Hour Slough
Two Approaches to Developing Applications
Visualforce Pages
Visualforce Components
Lightning Framework
Apex Controllers
Apex Triggers
Metadata API
REST API
Bulk API
Formula Fields
Validation Rules
Workflows and Approvals
Custom Objects
Custom Fields
Relationships
Page Layouts
Record Types
User
Interface
Business
Logic
Data
Model
Declarative Approach Programmatic Approach
Salesforce Entities: SObjects
• Entity-Level Security
• Field/Column Security
• Record-Level Security
• Mobile App UI
• Desktop Web UI
• Customizable UI
• REST API
• SOAP API
• Bulk API
• Push API
• Apex API
• New Entity (Object)
• Instantly Mobile Ready
• Instantly API Enabled for CRUD
• Show a Custom API
Demo
Two ways to build Mobile Apps
Customer-Facing
Mobile Services
Custom Mobile Apps
Employee-Facing
Out-of-the-box
AppExchange Apps:
Dropbox Concur Evernote ServiceMax More
Custom Apps and Integrations:
SAP Oracle Everything Custom More
Sales, Service and Marketing
Accounts Cases Campaigns Dashboards More
Salesforce1 Mobile App
Learn More…
Implementing Salesforce:
developer.salesforce.com
Opensource Engineering Projects:
Aura
github.com/forcedotcom/aura
Apache Phoenix
phoenix.apache.com
Top Related