Neo4j 1.0 Beta 7

A graph (mathematical lingo for a network) is a flexible data structure that allows a more agile and rapid style of development. You can think of Neo4j as a high-performance graph engine with all the features of a mature and robust database. The programmer works with an object-oriented, flexible network structure rather than with strict and static tables yet enjoys all the benefits of a fully transactional, enterprise-strength database.

In addition, Neo4j includes the usual database features: ACID transactions, concurrency control, transaction recovery, durable persistence, and everything else you would expect from an enterprise-strength database.

Major Features:

1. An intuitive graph-oriented model for data representation. Instead of static and rigid tables, rows and columns, you work with a flexible graph network consisting of nodes, relationships and properties.
2. Adisk-based, native storage manager completely optimized for storing graph structures for maximum performance and scalability.
3. Massive scalability. Neo4j can handle graphs of several billion nodes/relationships/properties on a single machine and can be shared to scale out across multiple machines.
4. A powerful traversal framework for high-speed traversals in the node space.
5. A small footprint. Neo4j is a single

Enhancements:

• API: Removed a number of deprecated methods (primarily for relationship type management) from EmbeddedNeas per warning in the previous release.
• API: Transaction is now an interface.
• API: TraversalPosition now has an isStartNode() method.
• API: NotFound and NotInTransaction runtime exceptions have been moved from internal impl package the api package.
• API: getRelationshipById is now exposed in NeoService.
• API: A common base interface for Node and Relationship has been added that contains the set/get/remove property operations.
• Core: Made it easy embed Neo4j in a Spring application. Spring can be configured to use Neo4js transaction manager.
• Core: All known bugs have been fixed.
• Core: Removed singletons and made everything IoC.
• Core: Lots of minor optimization and improvements above native store layer (nioneo).
• Core: Cleanup of code (removed non used code) and improved exception handling.
• Core: Improved read performance and parallelism by implementing MVCC-like features. Nlocks are now taken during read-only operations, instead concurrent operations are working against snapshot versions.