X.commerce Open Commerce Language (XOCL)

1,588 views
1,353 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,588
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Convergence!
  • X.commerce Open Commerce Language (XOCL)

    1. 1. X.commerce Open Commerce LanguageAnand Gangadharan, Product Management Jack Greenfield, Distinguished Architect
    2. 2. Outline• The Merchant Dilemma• Solution Architecture – Use best of breed components – Integrate them with a simple service bus – Standardize processes not documents• X.commerce platform – Define global choreographies using XOCL – Generate wire encodings, documentation, runtime metadata – Services implement local orchestrations – Service bus coordinates distributed transactions• A lap around XOCL• Current status6/13/2012 2
    3. 3. THE MERCHANT DILEMMA
    4. 4. Consumer Behavior is Changing Commerce Promotions & Location-based coupons services Mobile Self-scanning & commerce self-checkout Payments Mobile shopping lists In-store Social commerce research Loyalty6/13/2012 4
    5. 5. Blurring Online and Offline Today Tomorrow Mobile Local Online 6% Web- influenced Commerce Global Social Offline offline 37% Digital Service & delivery6/13/2012 5
    6. 6. SOLUTION ARCHITECTURE
    7. 7. Solutions Must Integrate Multiple TechnologiesMarketing channels Sales channels Fulfillment channels, Back office
    8. 8. Using a Service Bus Ad Hoc Integration Service Bus Merchant Service Merchant Service Systems Providers Systems ProvidersMerchant benefit: Access to new capabilities, lower switching costsDeveloper benefit: Exposure to new merchants, better cost amortization6/13/2012 8
    9. 9. Communication Architecture ????? Commerce semantics JSON Payload encoding REST/HTTP State transfer TCP/IP End to end connection6/13/2012 9
    10. 10. COMMERCE SEMANTICS
    11. 11. The Great Thing About Standards
    12. 12. The Problem With Documents
    13. 13. The Problem With Documents Lack of context• Different • Less than 3% of participants have document different • Aggregate behavior undefined • (n**2 – n)/2 requirements implementations for • Must be encoded n participants into unused Overloaded document fields Point to point properties agreements
    14. 14. Standardizing Processes Context specific Business signals• Define messages • Shared identity individual and • Just enough and lifecycle • Two phase aggregate data to commit behavior synchronize • Demonstrate state intent Global Private entity choreographies structure
    15. 15. Choreography and Orchestration Send 1 Receive 5 A D Receive 2 Send 6 Receive 1 B C Receive 3 Send 2 Send 4 Send 3 Send 5 Receive 4 • Global choreography can Receive 6 be audited • Local orchestrations can be automated with workflow engines6/13/2012 15
    16. 16. UN/CEFACT Modeling Methodology• No signals • Signal receipt • Response • Request is a query • Signal validation indicates success • Response is or failure results • May contain dataInform Notify Response Query
    17. 17. THE X.COMMERCE PLATFORM
    18. 18. X.commerce Open Commerce Language (XOCL) XOCL Commerce semantics JSON Payload encoding REST/HTTP State transfer TCP/IP End to end connection6/13/2012 19
    19. 19. X.commerce Open Commerce Language (XOCL) Specifications generate development • Parser artifacts • Serializer • Message Schemas • Editor • Metadata • Documentation • Mock Services Textual DSL based on XText6/13/2012 20
    20. 20. Processes Package Process Role Workflow• A process defines a set of roles and is implemented by one or more workflows.6/13/2012 Footnote information goes here 21
    21. 21. Transactions Package Calls Workflow Transaction Calls Role Sender Receiver Binds Topic• A workflow can call other workflows and/or transactions.• A transaction is an atomic exchange of Message messages between a sender role and a receiver role. 6/13/2012 Footnote information goes here 22
    22. 22. Types Package Type Has Message• A message has a type, and types may contain instances of other types.• Types defined in XOCL map 1 for 1 onto AVDL equivalents. 6/13/2012 Footnote information goes here 23
    23. 23. Contracts Package Capability Bundle Contract• A contract is a named set of roles.• A capability must implement all of the roles in a contract.• A bundle is a set of capabilities that Roles implements a set of contracts to enact one or more business processes. 6/13/2012 Footnote information goes here 24
    24. 24. Discovery Package X.com Process Role • Navigate package hierarchy • Search process, role and transaction descriptions Workflow6/13/2012 Footnote information goes here 25
    25. 25. What Roles Do I Play? Package X.com Contract • Capability developers choose contracts when they onboard. • Determines the topics they can publish and subscribe to. Role6/13/2012 Footnote information goes here 26
    26. 26. Implementing XOCL X.commerce Capabilities X.commerce FrameworksXOCL X.commerce Fabric
    27. 27. Multi-tenant commerce aware service bus Topic based broadcast/unicast publish/subscribe AVRO/JSON wire encoding Interprets XOCL metadata during execution Logs and enforces commerce processes X.commerce FabricAudits SLAs and reports exceptions Automates timeouts and coordinates commit
    28. 28. X.commerce Frameworks
    29. 29. X.commerce Capabilities• Product Information Management• Inventory Management• Customer Management• Order Management• Marketplace• Web Store• Email marketing
    30. 30. A LAP AROUND XOCL
    31. 31. NEXT STEPS
    32. 32. Get involved• Start here http://x.com/xocl• See you at GitHub https://github.com/xcommerce/XOCL – Go ahead, fork!

    ×