3. Salesforce.com services
500 million requests per day
60% of those calls are API calls
Thats 300 million API calls per day!
Over 98,000 Customers
Wednesday, October 5, 2011
4. Here is where we are today
Transactions per quarter (billions)
40
36 billion
30
All Trans
20 API Trans
10
0
Q3FY09 Q3FY10 Q3FY11 Q3FY12
Wednesday, October 5, 2011
5. Here is where we are going
Transactions per quarter (billions) 1
billion
100 per day
75
All Trans
50
36 billion API Trans
25
November, 2013
0
Q3FY09 Q3FY10 Q3FY11 Q3FY12 Q3FY13 Q3FY14
Wednesday, October 5, 2011
7. The API Raison D’etre
At first, so that customers could integrate other back office
applications.
Wednesday, October 5, 2011
8. The API Raison D’etre
At first, so that customers could integrate other back office
applications.
Later, so that customers and ISVs could extend CRM functionality.
Wednesday, October 5, 2011
9. The API Raison D’etre
At first, so that customers could integrate other back office
applications.
Later, so that customers and ISVs could extend CRM functionality.
And now, in addition to the two above, so that customers and ISVs
can build any other applications.
Wednesday, October 5, 2011
11. Historical Perspective
Prior to 2003, api documentation access
priced at $10,000.
Wednesday, October 5, 2011
12. Historical Perspective
Prior to 2003, api documentation access
priced at $10,000.
Post 2003, api documentation access became
free
Wednesday, October 5, 2011
13. Historical Perspective
Prior to 2003, api documentation access
priced at $10,000.
Post 2003, api documentation access became
free
2004 a free version of the environment was
provided
Wednesday, October 5, 2011
14. Historical Perspective
Prior to 2003, api documentation access
priced at $10,000.
Post 2003, api documentation access became
free
2004 a free version of the environment was
provided
2006 AppExchange was launched
Wednesday, October 5, 2011
15. Historical Perspective
Prior to 2003, api documentation access
priced at $10,000.
Post 2003, api documentation access became
free
2004 a free version of the environment was
provided
Every app in the
2006 AppExchange was launched AppExchange at
launch depended on
the API
Wednesday, October 5, 2011
17. API Strategy
Part 1: Keep the APIs as simple and flexible
as possible
Wednesday, October 5, 2011
18. API Strategy
Part 1: Keep the APIs as simple and flexible
as possible
Part 2: Enable integration between CRM and
back-office applications.
Wednesday, October 5, 2011
19. API Strategy
Part 1: Keep the APIs as simple and flexible
as possible
Part 2: Enable integration between CRM and
back-office applications.
Part 3: Enable vertical application
development and CRM extension
development
Wednesday, October 5, 2011
20. API Strategy
Part 1: Keep the APIs as simple and flexible
as possible
Part 2: Enable integration between CRM and
back-office applications.
Part 3: Enable vertical application
development and CRM extension
development
Part 4: Ensure that API maintains parity with
application and platform features
Wednesday, October 5, 2011
21. Historical Perspective
2001 - CRUD XML-RPC API
2003 - CRUD + Utility SOAP API v2.5
2004 - Metadata API
2005 - Async Metadata API
2006 - Ajax, join syntax
2007 - Custom web services, delegate authentication
2008 - Bulk API, outbound message api
2009 - Syndication API, file based metadata, feed and document API
2010 - Query in bulk, aggregates in SOAP, semi-join in SOAP, data.com API, REST API
2011 - Chatter API, streaming API, SOAP v23.0
> 2011 - Tooling API, radian 6 API(?), do.com API(?)
Wednesday, October 5, 2011
22. There is an API for that
• Web Services API (SOAP)
• Apex Web Services (Custom SOAP)
• Bulk API (REST)
• REST API
• Streaming API
• Apex REST API (Custom REST)
• Metadata API (SOAP)
• Chatter REST API
• Content API (SOAP)
• Data.com API (REST)
Wednesday, October 5, 2011
24. The Addition of REST
Emergence of HTML5
Wednesday, October 5, 2011
25. The Addition of REST
Emergence of HTML5
Momentum of Mobile Platforms
Wednesday, October 5, 2011
26. The Addition of REST
Emergence of HTML5
Momentum of Mobile Platforms
Perceived Modernity of Platform
Wednesday, October 5, 2011
27. The Addition of REST
Emergence of HTML5
Momentum of Mobile Platforms
Perceived Modernity of Platform
It’s the right technology for today
Wednesday, October 5, 2011
29. Chatter API
Chatter integration can be
“chatty”
Wednesday, October 5, 2011
30. Chatter API
Chatter integration can be
“chatty”
Wednesday, October 5, 2011
31. Chatter API
Chatter integration can be
“chatty”
Object based calls require
many queries to create a
single “feed”
Wednesday, October 5, 2011
32. Chatter API
Chatter integration can be
“chatty”
Object based calls require
many queries to create a
single “feed”
New approach returns full
object graph via REST
Wednesday, October 5, 2011
33. So, we have an API, we’re done, right?
You API history and future evolution reflects
your business’ history and future evolution.
or is it
You business’ history and future evolution
reflects your APIs history and future
Wednesday, October 5, 2011
