A retired Node.js client library for Neo4j graph database using its REST API.
Node-Neo4j was a Node.js driver for the Neo4j graph database, allowing developers to interact with Neo4j instances through its REST API. It provided asynchronous methods for creating nodes, managing relationships, and executing Cypher queries, facilitating graph-based data operations in JavaScript applications.
Node.js developers building applications that required graph database functionality with Neo4j, particularly those using Neo4j versions 1.5 to 2.1 before official JavaScript drivers were released.
It offered a lightweight, callback-based interface to Neo4j's REST API, with support for flow control libraries and Cypher queries, making it a practical choice for early Neo4j adopters in the Node.js ecosystem until Neo4j provided native drivers.
[RETIRED] Neo4j graph database driver (REST API client) for Node.js
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provided a straightforward way to interact with Neo4j's REST API before official JavaScript drivers existed, supporting versions 1.5 to 2.1 as noted in the README.
Leveraged Node.js's non-blocking I/O with callback-based functions for efficient HTTP requests, aligning with Node.js's core design for database interactions.
Allowed execution of Cypher queries, enabling access to Neo4j features like labels and constraints through its recommended query language.
Recommended integration with libraries like Streamline.js, async, or Step for managing complex asynchronous workflows, offering customization for developers.
The README explicitly states it's no longer under development since Neo4j 3.0 introduced an official driver, making it obsolete for current projects.
Only supports Neo4j up to version 2.1, missing modern features, security updates, and the Bolt protocol introduced in later versions.
Relies on callbacks rather than promises or async/await, which can lead to harder-to-maintain code and callback hell in complex applications.
Requires compilation from CoffeeScript and Streamline.js for development, adding overhead and potential debugging challenges, as detailed in the README.