Coin:Evolutionary and pervasive services - Digibiz'09


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Inside enterprice, all is more simple Outside is more complicated
  • Why democratic? Try to think to google. Google is nice but not democratic, google have information and use it for commercial scope, google use clustering of property deta. Here we have a public p2p approach.
  • Fast changing inside Registry, quite static data inside Repository
  • ISO standard, metamodels, models, evolutionistic
  • Coin:Evolutionary and pervasive services - Digibiz'09

    1. 1. Enterprise CO llaboration & IN teroperability Digibiz Evolutionary and Pervasive Service s 18 June 2009 Elia Conchione , Project Leader, Soluta.Net, Italy, EU e-mail : [email_address]
    2. 2. Problem <ul><li>Monetary policy in the United States
    3. 3. Global conseguences
    4. 4. Global financial crisis </li></ul>
    5. 5. SOA <ul><li>Inside an enterprise </li><ul><li>Trusted infrastructucure </li></ul><li>across enterprises </li><ul><li>Untrusted infrastructure </li></ul></ul>
    6. 6. Across enterprises <ul><li>Assumes not agreed IT model (aka WSDL)
    7. 7. Assumes not available service
    8. 8. Assumes not know business model (e.g. price/discount schema)
    9. 9. Assumes the infrastructure is shared </li><ul><li>Could compete! </li></ul></ul>
    10. 10. Actual DES <ul><li>Data are moved from service to db/repository </li><ul><li>Data replication, data inconsistency </li></ul><li>Repository contains data+end point </li><ul><li>Data obsolete
    11. 11. IP changes </li></ul><li>DOES NOT SCALE </li></ul>
    12. 12. Vision for the Internet of Services <ul><li>Strict alignment business-IT </li><ul><li>i.e. “what you see is what you get” </li></ul><li>Harvest and store separately </li><ul><li>Model and data </li></ul><li>Ipv4 docet </li><ul><li>DNS, decouple information from it's endpoint </li></ul><li>Decentralized architecture </li><ul><li>Democratic approach </li></ul></ul>
    13. 13. <ul><ul><li>Separation of concerns </li></ul></ul><ul><li>Models </li><ul><li>IT models (WSDL)
    14. 14. business models (schemas) </li></ul><li>Data: </li><ul><li>Endpoint & protocols
    15. 15. Business data (10% discount, €100 max price, 5% bulk volume discount)
    16. 16. Vendor information </li></ul></ul>
    17. 17. Architectural enabling decisions <ul><li>Repository </li><ul><li>Model
    18. 18. Decentralized architecture </li></ul><li>Registry </li><ul><li>Data
    19. 19. Decentralized architecture: by adoption of p2p topology </li></ul><li>Datawarehouse </li><ul><li>data mining (as Google leverages DNS , data from web servers are grabbed by bots using DNS, the registry)
    20. 20. this is not an infrastructural element </li></ul></ul>
    21. 21. COIN strategical approach
    22. 22. Repository
    23. 23. Registry RegistryEntry is the object that is stored inside the P2P Registry network. The Supplier object contains information about the Company that provides the service.
    24. 24. Lease management The lease is managed by the Registry, that is responsible for checking if a services is still available. Each service has to provide a special operation , that returns a response to a “check” request. When a service doesn't respond, its entry is automatically deleted from the Registry.
    25. 25. Datawarehouse <ul><li>data mining (as Google leverages DNS , data from web servers are grabbed by bots using DNS, the registry)
    26. 26. this is not an infrastructural element </li></ul>
    27. 27. The COIN Integrator <ul><li>More easy to use
    28. 28. Standard interface </li></ul>
    29. 29. Conclusions <ul><li>Repository saw for reuse </li><ul><li>IT and business models </li></ul><li>Saw for interoperability </li><ul><li>Naturally evolves
    30. 30. Convergent models </li></ul><li>Registry </li><ul><li>Advertise available services
    31. 31. DynamicDNS </li></ul><li>Datawarehouse </li><ul><li>Enables complex researches
    32. 32. Caching .. </li></ul><li>It can be done for services what Google is doing for the Information </li></ul>
    33. 33. Q&A <ul><li>visit
    34. 34. contact the author [email_address]
    35. 35. visit
    36. 36. Thank you! </li></ul>