Your SlideShare is downloading. ×
SOA India 2009 | SOA and Web Business Platforms
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

SOA India 2009 | SOA and Web Business Platforms

867
views

Published on

Web businesses such as eBay®, Amazon® and a whole lot of others have long seized to be mere websites; they have morphed into web business platforms. By adopting a platform strategy, they are building …

Web businesses such as eBay®, Amazon® and a whole lot of others have long seized to be mere websites; they have morphed into web business platforms. By adopting a platform strategy, they are building an ecosystem of developers, partners and entrepreneurs to build innovative applications for customers. In this session, we discuss the significance of and associated issues in adopting a SOA strategy to open-up these platforms for the ecosystem.

Published in: Design, Technology, Business

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
867
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SOA and the Web Business Platforms Harsh Jegadeesan, Ph.D.
  • 2. Context
    • Evolution of the Web
      • Read-only Web to Read-write web
    • Emergence of Web Business Platforms
  • 3. Platform Usage Scenario | Website Traditional Scenario
  • 4. Platform Usage Scenario | Mashups + + -Informational - Lightweight
  • 5. Platform Usage Scenario | Composites -Transactional - Heavyweight
  • 6. Platform Usage Scenario | Integration Scenario 2: Auctioning Excess Inventory Scenario 1: Selling on eBay Scenario 3: Integrating Synergistic Applications ERP HCM Integration of cloud apps with on-premise apps
  • 7. Platform Usage Scenario | Access Channels
    • Content Syndication
    • Productivity Environments
  • 8. Emerging Business Models
    • Monetizing APIs
    • Revenue Share from Transactions (Paypal, eBay)
    • Sell advertisements
    • Affiliates & Partners
    • Revenue from traffic generation
    • Advertising
    • Subscriptions
    For Platform Providers For Platform Users
  • 9. Web Business Platforms | Stakeholders Developers Aggregators Marketplaces End-Users Web Business Platform Platform Providers Entrepreneurs
  • 10. The Platform Strategy
    • Opening-up of the platform using web APIs (~WinAPIs)
    • Platform Adoption and creation of an ecosystem around the platform
      • Address needs of heterogeneous platform users
      • Support for different technology platforms
  • 11. The Case for Platform Strategy
    • Expand footprint of platform
    • Drive traffic
    • Innovation / Feature Development
    • Support new Business Models
    • Content Acquisition (User-Generated Content)
    • Co-Branding
  • 12. web API Requirements
    • Support for heterogenous technlogy platforms
      • Support for open-standards
    • Architecture homogenity and conceptual coherance
    • Must follow underlying domain semantics
    • Easy to learn
    Web APIs = Webservices SOAP, XML, HTTP, PoX, WS-* SOA, REST
  • 13. Engineering Challenges | Granularity
    • API Granularity
      • Fine-Granular APIs
        • Nouns. E.g. Orders, Customers
        • Used by Mashups
      • Coarse-Granular APIs
        • Verbs. E.g.ATP Check
        • Used for integration, by composites
  • 14. Engineering Challenges | Technology Choices Source: The SOA with reach: Web-Oriented Architecture, Dion Hinchcliffe Technology choices must be made based on application requirements
  • 15. Engineering Challenges | Evolving Standards
    • Challenge: Catering to heterogeneous platform users
    SOAP vs. REST WS-* XML / JSON OASIS / W3C Evolving Standards Problem Model -Driven development (MDD) can help safeguard investments
  • 16. Engineering Challenges | Consumption SDKs
    • Catering to heterogenous service consumers
      • Transport Protocols
      • Data Standards
    • Maintaining and Evolving language-specific Software Development Kits (SDKs)
    Consumption SDKs can be created from conceptual models built using MDD
  • 17. Concluding Remarks
    • Evolution of the web – Web Business Platforms
    • Strong business case to adopt platform strategy
    • Platforms opening-up through web APIs
    • web APIs = webservices
    • Engineering Challenges; can be addressed using MDA
    Thanks! Any questions? Mail to: [email_address]