1. Overview
Chapter Contents
|
Prev
|
Next
Keyword Search:
www.openlinksw.com
docs.openlinksw.com
Book Home
Contents
Preface
Overview
What is Virtuoso?
Why Do I Need Virtuoso?
Key Features of Virtuoso
Virtuoso 6 FAQ
Installation Guide
Quick Start & Tours
Sample ODBC & JDBC Applications
Conceptual Overview
Administration
Data Access Interfaces
SQL Reference
SQL Procedure Language Guide
Database Event Hooks
Data Replication, Synchronization and Transformation Services
Web Application Development
XML Support
RDF Data Access and Data Management
Web Services
Runtime Hosting
Internet Services
Free Text Search
TPC C Benchmark Kit
Using Virtuoso with Tuxedo
Appendix
Virtuoso Functions Guide
Abstract
A quick overview on Virtuoso providing answers to simple questions that may already be in mind.
Table of Contents
1.1. What is Virtuoso?
1.2. Why Do I Need Virtuoso?
1.3. Key Features of Virtuoso
1.3.2. XML Document Storage & Creation
1.3.3. Web Page Hosting
1.3.4. Web Services Creation & Hosting
1.3.5. WebDAV Compliant Web Store
1.3.6. Content Replication & Synchronization
1.3.7. Transparent Access To Heterogeneous Data
1.3.8. Mail Delivery & Retrieval Services
1.3.9. NNTP Aggregation & Serving
1.4. Virtuoso 6 FAQ
1.4.1. What is the storage cost per triple?
1.4.2. What is the cost to insert a triple (for the insertion itself, as well as for updating any indices)?
1.4.3. What is the cost to delete a triple (for the deletion itself, as well as for updating any indices)?
1.4.4. What is the cost to search on a given property?
1.4.5. What data types are supported?
1.4.6. What inferencing is supported?
1.4.7. Is the inferencing dynamic, or is an extra step required before inferencing can be used?
1.4.8. Do you support full-text search?
1.4.9. What programming interfaces are supported? Do you support standard SPARQL protocol?
1.4.10. How can data be partitioned across multiple servers?
1.4.11. How many triples can a single server handle?
1.4.12. What is the performance impact of going from the billion to the trillion triples?
1.4.13. Do you support additional metadata for triples, such as time-stamps, security tags etc?
1.4.14. Should we use RDF for our large metadata store? What are the alternatives?
1.4.15. How multithreaded is Virtuoso?
1.4.16. Can multiple servers run off a single shared disk database?
1.4.17. Can Virtuoso run on a SAN?
1.4.18. How does Virtuoso join across partitions?
1.4.19. Does Virtuoso support federated triple stores? If there are multiple SPARQL end points, can Virtuoso be used to do queries joining between these?
1.4.20. How many servers can a cluster contain?
1.4.21. How do I reconfigure a cluster, adding and removing machines, etc?
1.4.22. How will Virtuoso handle regional clusters?
1.4.23. Is there a mechanism for terminating long running queries?
1.4.24. Can the user be asynchronously notified when a long running query terminates?
1.4.25. How many concurrent queries can Virtuoso handle?
1.4.26. What is the relative performance of SPARQL queries vs native relational queries?
1.4.27. Does Virtuoso Support Property Tables?
1.4.28. What performance metrics does Virtuoso offer?
1.4.29. What support do you provide for concurrent/multithreaded operation? Is your interface thread-safe?
1.4.30. What level of ACID properties is supported?
1.4.31. Do you provide the ability to atomically add a set of triples, where either all are added or none are added?
1.4.32. Do you provide the ability to add a set of triples, respecting the isolation property (so concurrent accessors either see none of the triple values, or all of them)?
1.4.33. What is the time to start a database, create/open a graph?
1.4.34. What sort of security features are built into Virtuoso?
Previous
Preface
Chapter Contents
Next
What is Virtuoso?