eBay - Enabling Connected Commerce

Preview:

DESCRIPTION

Connected Commerce @ eBay demands that marketplaces data and business policies be exposed coherently and seamlessly to all participants, using any platform on any device. This presentation will cover the evolution of APIs at eBay and how they are tackling the problem of enabling app developers to easily build a complete marketplaces shopping experience on any device using any platform.

Citation preview

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

2

WE ARE AT AN INFLECTION POINTTECHNOLOGY DRIVING CHANGE IN BEHAVIOR

NO MORE ONLINE OR OFFLINE – JUST SHOPPING

UNPRECEDENTED ACCESS TO GOODS

BOTTOM LINE – PEOPLE EXPECT MORE

3

The “Great Shift” to Devices

4

ebay going mobile - GMB Q1’12 – Q2’13

30%

20%

10% Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013

5

Multi-screen experience is the future of commerce

Source: Google

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

7

HOWEVER

8

Multiscreen Search

9

Multi-screen Item Details

10

How did we get here?

THIRD PARTY APPS MAINSTREAM WEB

11

Applications

svc svc svc

svcsvc

svc

svc

svc

svc

svc svc

svcsvc

svc

svcsvc

Checkout My eBay Catalog Selling Search

Service Providers

M x N Complexity makes App developer unproductive

How have we evolved over time?

12

And where are we currently?

300 + APIs

500 + INTERNAL SERVICES

HARD TO DISCOVER

INCONSISTENT BEHAVIOR (ERROR CODES, LOCALIZATION, HEADER INFO . ..)

APIS ARE INEFFICIENT TO USE

INCONSISTENT DATA VALUES BETWEEN DIFFERENT SERVICES

13

Program Functions

ARCHITECTURE GOVERNANCEEVANGELISM & ADVOCACY

FOUNDATIONS

COMMERCE OS

SERVICES PORTFOLIO

14

Architecture

1. ERROR & EXCEPTION HANDLING

2. BASE REQUEST AND RESPONSE

3. VERSIONING

4. COMMON TYPES

5. EXPERIMENTATION

6. ADDRESSING AND URLS

7. INTERNATIONALIZATION

8. IDM

9. NAMESPACES AND NAMING CONVENTIONS

10. TRACKING

11. INSTRUMENTATION

12. SECURE ACCESS

13. REST GUIDELINES

14. SELF TEST UNIT TEST

15. STORAGE AND DATA

16. MODELING

17. INTEGRATION WITH SYSTEM MONITORING

18. OPERATION, ADMIN, INITIALIZATION, CONFIG

19. IDENTITIES

20. EVENTS AND MESSAGING

21. RELEASE MANAGEMENT

22. MIGRATION

23. MULTI TENANCY

24. SERVICE MODE/ASYNC SERVICES

25. CODE BOUNDARIES AND ENCAPSULATION

IDENTIFY

DEFINE

IMPLEMENT ON PLATFORMS

ADOPTION IN SERVICES

SERVICE STANDARDS

15

Governance

STANDARDS GOVERNANCE

SERVICES GOVERNANCE

TYPE SPACE GOVERNANCE

ASSET PORTFOLIO REVIEW

INTERFACE DEVELOPMENT METHOD

ENGINEERING HUDDLES

16

Services Portfolio

17

Evangelism and Advocacy

• TRAININGS – DESIGNING AND IMPLEMENTING SERVICES

• SERVICES BROWNBAGS

• PUBLISH CAPABILITIES

• PROMOTE ADOPTION

• IDENTIFY GAPS

18

Foundations

• PORTFOLIO MANAGEMENT

• ASSET REPOSITORY

• SERVICES AND TYPE DISCOVERY

• SERVICE STANDARD ASSESSMENTS

• ALERTING AND MONITORING

• MEASURING DEVELOPER EFFICIENCY

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

Thank you

Recommended