Neocons is a feature rich idiomatic Clojure client for the Neo4J REST API.
Neocons currently supports the following features (all via REST API, so you can use open source Neo4J Server edition for commercial projects):
- Create, read, update and delete nodes
- Create, read, update and delete relationships
- Fetch relationships for given node
- Create and delete indexes
- Index nodes
- Query node indexes for exact matches and using full text search queries
- Query automatic node index
- Traverse nodes, relationships and paths
- Find shortest path or all paths between nodes
- Predicates over paths, for example, if they include specific nodes/relationships
- Cypher queries
- Basic HTTP authentication, including Heroku Neo4J add-on compatibility
- Efficient multi-get via Cypher queries
- Convenience functions for working with relationships and paths
- Neo4J 2.0 transactions
- Neo4J 2.0 labels
- Neo4J 2.0 constraints
To get started and see what using Neocons feels like, please use our Getting started with Clojure and Neo4J Server guide.
Neocons has a mailing list. Feel free to join it and ask any questions you may have.
To subscribe for announcements of releases, important changes and so on, please follow @ClojureWerkz on Twitter.
Neocons is not a young project: first released in October 2011, it is over 2 years old, with active production use from week 1.
It now supports Neo4j 2.0 release and the API is quite stable. Documentation is in good shape, too.
Neocons artifacts are released to Clojars. If you are using Maven, add the following repository
definition to your
<repository> <id>clojars.org</id> <url>http://clojars.org/repo</url> </repository>
<dependency> <groupId>clojurewerkz</groupId> <artifactId>neocons</artifactId> <version>2.0.1</version> </dependency>
CI is hosted by travis-ci.org
Neocons requires Clojure 1.4+. The most recent stable Clojure release is highly recommended.
2.0 tracks Neo4J Server 2.0 changes, although currently
the test suite also passes against 1.9.x.
There are incompatible changes in 1.9 and 2.0 in mutating Cypher syntax, so Neo4j Server 1.8 compatibility is less than perfect.
1.1 supports Neo4J Server 1.5.0 and later versions. For the
support, 1.6 is the minimum recommended versions because Cypher is
supported by the REST API directly without any plugins. Some features
(in Cypher in particular) may be specific to a later version. We
recommend using the most recent stable release. Neocons is actively
tested against bleeding edge Neo4J Server snapshots and we try to
support important new features before stable server releases come out.
If you use OpsCode Chef, there is a Neo4J Server Chef cookbook.
Neocons uses Leiningen 2. Make sure you have it installed and then run tests against all supported Clojure versions using
lein2 all test
Then create a branch and make your changes on it. Once you are done with your changes and all tests pass, submit a pull request on Github.
Copyright (C) 2011-2014 Michael S. Klishin, Alex Petrov
Because Neo4J is GPL software, linking against it will require your project to be open source. While there are perfectly valid use cases for this, Neocons was developed to be used in commercial projects and Neocons authors strongly prefer business-friendly licenses and Clojure community commitment to the Eclipse Public License v1.
Neocons namespace structure leave the door open for future Neo4J Server features like the binary protocol but it is highly unlikely that it will ever cover embedding, should Neo4J license stay GPL forever.