Sri Gopalakrishnan discusses how eBay is evolving to enable connected commerce across multiple devices. He notes that technology is driving changes in consumer behavior, with people now expecting seamless access to goods on any device. eBay has seen rapid growth in mobile usage, with 30% of transactions coming from mobile by mid-2013. Gopalakrishnan outlines eBay's vision of connected commerce, where business processes and data are exposed coherently across all participants and devices. However, eBay's current architecture of 300+ APIs and 500+ internal services is difficult for developers to use. eBay is implementing a "Commerce OS" to standardize services, data models and governance to better support multi-device connected commerce.

1. eBay – Enabling Connected Commerce
Sri Gopalakrishnan – Director of Engineering, eBay

2. WE ARE AT AN
INFLECTION POINT
TECHNOLOGY DRIVING CHANGE IN BEHAVIOR
NO MORE ONLINE OR OFFLINE – JUST SHOPPING
UNPRECEDENTED ACCESS TO GOODS
BOTTOM LINE – PEOPLE EXPECT
MORE
2

3. The “Great Shift” to Devices
3

4. ebay going mobile - GMB Q1’12 – Q2’13
30%
20%
10%
Q1 2012
Q2 2012
Q3 2012
4
Q4 2012
Q1 2013
Q2 2013

5. Multi-screen experience is the future of commerce
Source: Google
5

6. Connected Commerce
Demands data and business
processes to be exposed
coherently and seamlessly to
- All participants
- Using any platform
- Via any device
CONNECTED COMMERCE
6

7. HOWEVER
7

8. Multiscreen Search
8

9. Multi-screen Item Details
9

10. How did we get here?
THIRD PARTY APPS
MAINSTREAM WEB
10

11. How have we evolved over time?
Checkout
My eBay Catalog
Selling
Search
Service Providers
svc
svc
svc
svc
svc
svc
svc
svc
svc
svc
svc
svc
Applications
M x N Complexity
makes App developer unproductive
11
svc
svc
svc
svc

12. And where are we currently?
300 + APIs
500 + INTERNAL SERVICES
HARD TO DISCOVER
INCONSISTENT BEHAVIOR (ERROR CODES, LOCALIZATION,
HEADER INFO . ..)
INCONSISTENT DATA VALUES BETWEEN DIFFERENT SERVICES
APIS ARE INEFFICIENT TO USE
12

13. Program Functions
COMMERCE OS
ARCHITECTURE
GOVERNANCE
SERVICES PORTFOLIO
13
EVANGELISM
& ADVOCACY
FOUNDATIONS

14. Architecture
1. ERROR & EXCEPTION HANDLING
14. SELF TEST UNIT TEST
SERVICE STANDARDS
2. BASE REQUEST AND RESPONSE
15. STORAGE AND DATA
IDENTIFY
3. VERSIONING
16. MODELING
4. COMMON TYPES
17. INTEGRATION WITH SYSTEM
MONITORING
5. EXPERIMENTATION
18. OPERATION, ADMIN, INITIALIZATION, CO
NFIG
6. ADDRESSING AND URLS
20. EVENTS AND MESSAGING
9. NAMESPACES AND NAMING
CONVENTIONS
10. TRACKING
21. RELEASE MANAGEMENT
22. MIGRATION
23. MULTI TENANCY
24. SERVICE MODE/ASYNC SERVICES
11. INSTRUMENTATION
12. SECURE ACCESS
IMPLEMENT ON PLATFORMS
ADOPTION IN SERVICES
19. IDENTITIES
7. INTERNATIONALIZATION
8. IDM
DEFINE
25. CODE BOUNDARIES AND
ENCAPSULATION
13. REST GUIDELINES
14

15. Governance
STANDARDS GOVERNANCE
SERVICES GOVERNANCE
TYPE SPACE GOVERNANCE
ASSET PORTFOLIO REVIEW
INTERFACE DEVELOPMENT METHOD
ENGINEERING HUDDLES
15

16. Services Portfolio
16

17. Evangelism and Advocacy
• TRAININGS – DESIGNING AND IMPLEMENTING SERVICES
• SERVICES BROWNBAGS
• PUBLISH CAPABILITIES
• PROMOTE ADOPTION
• IDENTIFY GAPS
17

18. Foundations
• PORTFOLIO MANAGEMENT
• ASSET REPOSITORY
• SERVICES AND TYPE DISCOVERY
• SERVICE STANDARD ASSESSMENTS
• ALERTING AND MONITORING
• MEASURING DEVELOPER EFFICIENCY
18

19. Bottomline
• WEB IS NO LONGER THE PRIMARY CHANNEL FOR REVENUE GROWTH
• APIs ARE CRITICAL FOR AN ORGANIZATION’S RELEVANCE
• SOLVING FOR DEVELOPER EFFICIENCY IS CRITICAL FOR SUCCESS
• TOP DOWN UNILATERAL EXECUTIVE SUPPORT AND LASER FOCUS
19

20. Thank you