Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

The Web of Data as a Massively Scalable NoSQL Database


Published on

Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. It leverages …

Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. It leverages fundamental characteristics of Web architecture (loose coupling, decentralization, simple and well defined access patterns) and builds on RDF (a W3C standard data model). We'll give a brief overview of RDF and show how Linked Data principles decouple its use for interoperability and data modelling from the "heavyweight" Semantic Web baggage that has long been considered a barrier to entry.

The characteristics that allowed the Web to scale so quickly and widely include decentralization, a massively distributed architecture, an absence of integrity constraints, and weak guarantees about consistency. The Web of data aims to achieve the same end for data, promoting it to a first class Web citizen and making linking data as easy and ubiquitous as linking HTML documents. Many of the same characteristics that make the Web so successful and scalable also apply to the Web of Data.

The rise of NoSQL databases is a response to the changing requirements of Web scale data. Typically these databases deliver performance at scale by relaxing consistency guarantees, eschewing transactions, using flexible data models and distributed architectures, and placing constraints on access patterns. Linked Data and RDF turn the Web itself into a decentralized and massively scalable sparse column store with globally identifiable column names; an enormous, globally distributed repository of linked, structured data.

In this talk we will highlight the common characteristics of various flavors of NoSQL database and the Web of Data. We will also discuss important differences, and outline the trade-offs involved when deciding on a storage solution for your application data, such as the importance of query performance, availability or ACID transactions. We will be delving into concerns around:

Data portability
Common query languages
Tool chain interoperability

Published in: Technology, Sports

  • 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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. The Web of Data as a NoSQL Database Sam Tunnicliffe @beobal Talis Systems Ltd NoSQL Now! 2011
  • 2. entity retrievalusing xDBC & ORM or custom SQL version 1.0
  • 3. entity retrievalusing store specific protocols and clients schema-last
  • 4. sharding strategy may be encapsulated schema knowledge by clients/servers orresides in application may require the or access layer application to handle routing/addressing as well as managing store specific protocols and clients sharded, polyglot storage
  • 5. What if you could use the Web as a database?
  • 6. loose coupling
  • 7. outsource dataacquisition costs
  • 8. proven, extreme scalability
  • 9. leverage existing infrastructure
  • 10. more and more diverse data
  • 11. serendipity
  • 12. high latency
  • 13. giving away control
  • 14. variable availability
  • 15. global names
  • 16. 1969-059Aglobal names
  • 17. 1969-059A spacecraft/1969-059Aglobal names
  • 18. 1969-059A spacecraft/1969-059A names
  • 19. 1969-059A spacecraft/1969-059A for entity names
  • 20. mass 28801.1things have attributes
  • 21. mass 28801.1 name “Apollo 11 CSM”things have attributes
  • 22. mass 28801.1 name “Apollo 11 CSM” launch launch/1969-059things have attributes
  • 23. 28801.1 “Apollo 11 CSM” launch/1969-059URIs for attribute names
  • 24.
  • 25. dereference to get data
  • 26. DNS is your routing component
  • 27. subject predicate objectRDF and linked data
  • 28. 1969-59A launch launch/1969-59RDF and linked data
  • 29. 1969-59Amass: 28801.1name: Apollo 11 CSM launch launch/1969-59 launch date: 16 July 1969 launch vehicle: Saturn V RDF and linked data weather: clear, dry
  • 30. 1969-059A Apollo 11 Capelaunch/1969-59 Canaveral Washington D.C. launch date: 16 July 1969 launch vehicle: Saturn V weather: clear, dry United Mexico States alternate name: Stati Uniti alternate name: Estados Unidos alternate name: アメリカ合衆国 population: 311,874,000 RDF and linked data Canada
  • 31. routes betweenlinked entities is explicit in data DNS does the hard work entity lookups come from authoritative sources web enabled data
  • 32. realtime discovery of additional data sourcesweb enabled data
  • 33. expandeddata universe simplified access protocol but some things are now outside of your control web enabled data
  • 34. local caches
  • 35. outcomes
  • 36. shared effort
  • 37. more simple data integration
  • 38. more linked data
  • 39. effects
  • 40. use the web as a database by...● using global names ● for entities ● for attributes● using standard formats● making data dereferenceable● linking to other data
  • 41. http://talis.comthank you