allegrograph: All content tagged as allegrograph in NoSQL databases and polyglot persistence
The main page of InfiniteGraph, a graph database commercialized by Objectivity, features an interesting comparison of 7 graph databases (InfiniteGraph, Neo4j, AllegroGraph, Titan, FlockDB, Dex, OrientDB) based on 16 criteria: licensing, source, scalability, graph model, schema model, API, query method, platforms, consistency, concurrency (distributed processing), partitioning, extensibility, visualizing tools, storage back end/persistency, language, backup/restore.
Unfortunately the image is almost unreadable, but Peter Karussell has extracted the data in a GoogleDoc spreadsheet embedded below.
Original title and link: A Comparison of 7 Graph Databases ( ©myNoSQL)
Patrick Durusau mentioned on his blog a new record set by Franz’s AllegroGraph: 1 trillion RDF triples. This comes only 2 months after the previous Franz’s AllegroGraph record of 310 billion triples.
My first thought was: why is this important? It was one of the few times I’ve found the answer in the PR announcement:
A trillion RDF Statements […] is a primary interest for companies like Amdocs that use triples to represent real-time knowledge about telecom customers. Per-customer, Amdocs uses about 4,000 triples, so a large telecom like China Mobile would easily need 2 trillion triples to have detailed knowledge about each single customer.
Original title and link: 1 Trillion RDF Triples With Franz’s AllegroGraph ( ©myNoSQL)
- AllegroGraph is 100 percent ACID, supporting Transactions: Commit, Rollback, and Checkpointing. See the new tutorials for the Java and Python clients
- Full and Fast Recoverability
- 100% Read Concurrency, Near Full Write Concurrency
- Online Backups
- Dynamic and Automatic Indexing – All committed triples are always indexed (7 indices)
- Advanced Text Indexing – Lucene style but faster, text indexing per predicate. See the new tutorials for the Java and Python clients
- Duplicate Triple deletion while indexing
- All Clients based on http REST Protocol – Java, Sesame, Jena, and Python
- Completely multi-processing based (SMP) – Automatic Resource Management for all processors and disks, and optimized memory use. See the new performance tuning guide here, and new server configuration guide here
- Column-based compression of indices similar to column-based RDBMS – reduced paging, better performance
- Dedicated and Public Sessions – In dedicated sessions users can work with their own rule sets against the same database
- Python Client Improvements – We now provide a full Python interface. The API is based on the Java Sesame interface and includes Spatial-Temporal and Social Network support
- LUBM Benchmarks – Updated for this release
Pere Urbón ☞ published a short review of a couple of existing graph databases. For your reference, below are the ones reviewed in the post and a couple more that we’ve previously mentioned here on myNoSQL:
☞ Neo4j is an embedded, disk-based, fully transactional Java persistence engine that stores data structured in graphs rather than in tables.
☞ DEX is a high performance library to manage very large graphs or networks
☞ HyperGraphDB: a general purpose, extensible, portable, distributed, embeddable, open-source data storage mechanism.
☞ InfoGrid: an Internet Graph Database with a many additional software components that make the development of REST-ful web applications on a graph foundation easy.
☞ vertexdb: a high performance graph database server that supports automatic garbage collection.
Note: by checking the project homepage I cannot tell if the project is still active or not.
☞ AllegroGraph RDFStore: a modern, high-performance, persistent RDF graph database.
Note: AllegroGraph seems to be positioned in the RDF stores space, which features some other solutions too.
☞ Filament: a graph persistence framework and associated toolkits based on a navigational query style.
☞ Sones GraphDS provides an inherent support for high-level data abstraction concepts (graph structures, walks, consistency, editions, revisions, copies), its own Graph Query Language, an underlying distributed file system and various interfaces like SOAP, REST or WebDAV.
And I’m not sure these are all …
Update: make sure you check the NoSQL Graph Database Matrix