@irongraph/node-linux-arm64-gnu 0.1.8 → 0.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +29 -35
- package/irongraph.linux-arm64-gnu.node +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# IronGraph for Node.js
|
|
2
2
|
|
|
3
|
-
**
|
|
3
|
+
**Embeddable Cypher graph database with sub-µs point reads, built-in streams, queues, and local text embeddings. Node.js SDK.**
|
|
4
4
|
|
|
5
5
|
Use Cypher to query graph structure, search text and vectors, inspect property history, and
|
|
6
6
|
administer the database. Built-in Kafka-compatible Streams and AMQP-compatible Queues handle event
|
|
@@ -8,40 +8,6 @@ and message workloads. `@irongraph/node` provides native embedded access, remote
|
|
|
8
8
|
clients, and TypeScript declarations for Node.js. IronGraph is open-source software released under
|
|
9
9
|
the Apache License 2.0.
|
|
10
10
|
|
|
11
|
-
## Performance at a glance
|
|
12
|
-
|
|
13
|
-
Graph queries execute on the CPU against one shared canonical graph. Local text inference can
|
|
14
|
-
use Metal or CUDA independently. Measure complete queries separately from individual graph operations;
|
|
15
|
-
latency depends on the workload, graph size, indexes, and host.
|
|
16
|
-
|
|
17
|
-
## Database capabilities
|
|
18
|
-
|
|
19
|
-
| Capability | What you can do |
|
|
20
|
-
| --- | --- |
|
|
21
|
-
| **Graph queries and analytics** | Match relationships and paths with Cypher; run shortest paths, PageRank, connected components, and community detection. |
|
|
22
|
-
| **Temporal properties and analysis** | Retain property history, read values with `AT TIME`, inspect samples with `HISTORY`, and aggregate with time windows and maintained rollups. |
|
|
23
|
-
| **Text documents and search** | Store the full text of articles, notes, manuals, and other written content on graph nodes; search that text with text and vector indexes and automatic local embeddings. |
|
|
24
|
-
| **Built-in Kafka-compatible Streams** | Produce and consume events through supported Kafka clients; manage topics, partitions, retention, and consumer-lag monitoring. |
|
|
25
|
-
| **Built-in AMQP-compatible Queues** | Use classic and stream queues, direct/fanout/topic exchanges, bindings, and retention with supported AMQP clients. |
|
|
26
|
-
|
|
27
|
-
Cypher handles graph operations, temporal analysis, search, and stream/queue administration.
|
|
28
|
-
Message producers and consumers use the supported Kafka or AMQP protocols through the instance's
|
|
29
|
-
configured listeners. The SDK query interface does not replace those protocol clients.
|
|
30
|
-
|
|
31
|
-
Explicit projects and the `OBSERVED`, `KNOWLEDGE`, and `WORKSPACE` layers organize data.
|
|
32
|
-
Indexes and unique constraints, transactions, asynchronous write-ahead logging, recovery, and
|
|
33
|
-
periodic snapshots are part of the database.
|
|
34
|
-
|
|
35
|
-
The standalone instance serves its web console at
|
|
36
|
-
[http://127.0.0.1:18484/web/](http://127.0.0.1:18484/web/) by default and also supports local MCP
|
|
37
|
-
access. Start the official standalone distribution before opening that address. Opening an
|
|
38
|
-
embedded database through Python, Node.js, or Rust does not start a web server or expose the
|
|
39
|
-
console. For a configured remote instance, use its HTTPS address followed by `/web/`, with
|
|
40
|
-
the required browser-managed client certificate.
|
|
41
|
-
|
|
42
|
-
Temporal reads apply to declared properties within their retention window. Graph topology and
|
|
43
|
-
ordinary properties are read in their current state.
|
|
44
|
-
|
|
45
11
|
## Install
|
|
46
12
|
|
|
47
13
|
You need Node.js 20.17 or later and an official package. Native release targets are macOS 15+
|
|
@@ -118,6 +84,34 @@ certificate-authority paths. Remote connections require mutual TLS and project a
|
|
|
118
84
|
plain connections are loopback-only. For a browser or React application, use
|
|
119
85
|
`@irongraph/client` to connect to a running instance.
|
|
120
86
|
|
|
87
|
+
## Database capabilities
|
|
88
|
+
|
|
89
|
+
| Capability | What you can do |
|
|
90
|
+
| --- | --- |
|
|
91
|
+
| **Graph queries and analytics** | Match relationships and paths with Cypher; run shortest paths, PageRank, connected components, and community detection. |
|
|
92
|
+
| **Temporal properties and analysis** | Retain property history, read values with `AT TIME`, inspect samples with `HISTORY`, and aggregate with time windows and maintained rollups. |
|
|
93
|
+
| **Text documents and search** | Store the full text of articles, notes, manuals, and other written content on graph nodes; search that text with text and vector indexes and automatic local embeddings. |
|
|
94
|
+
| **Built-in Kafka-compatible Streams** | Produce and consume events through supported Kafka clients; manage topics, partitions, retention, and consumer-lag monitoring. |
|
|
95
|
+
| **Built-in AMQP-compatible Queues** | Use classic and stream queues, direct/fanout/topic exchanges, bindings, and retention with supported AMQP clients. |
|
|
96
|
+
|
|
97
|
+
Cypher handles graph operations, temporal analysis, search, and stream/queue administration.
|
|
98
|
+
Message producers and consumers use the supported Kafka or AMQP protocols through the instance's
|
|
99
|
+
configured listeners. The SDK query interface does not replace those protocol clients.
|
|
100
|
+
|
|
101
|
+
Explicit projects and the `OBSERVED`, `KNOWLEDGE`, and `WORKSPACE` layers organize data.
|
|
102
|
+
Indexes and unique constraints, transactions, asynchronous write-ahead logging, recovery, and
|
|
103
|
+
periodic snapshots are part of the database.
|
|
104
|
+
|
|
105
|
+
The standalone instance serves its web console at
|
|
106
|
+
[http://127.0.0.1:18484/web/](http://127.0.0.1:18484/web/) by default and also supports local MCP
|
|
107
|
+
access. Start the official standalone distribution before opening that address. Opening an
|
|
108
|
+
embedded database through Python, Node.js, or Rust does not start a web server or expose the
|
|
109
|
+
console. For a configured remote instance, use its HTTPS address followed by `/web/`, with
|
|
110
|
+
the required browser-managed client certificate.
|
|
111
|
+
|
|
112
|
+
Temporal reads apply to declared properties within their retention window. Graph topology and
|
|
113
|
+
ordinary properties are read in their current state.
|
|
114
|
+
|
|
121
115
|
## License
|
|
122
116
|
|
|
123
117
|
IronGraph is licensed under the Apache License 2.0. Third-party components and the embedding model
|
|
@@ -1,4 +1,4 @@
|
|
|
1
1
|
[diffend] Oversized file quarantined before diffing.
|
|
2
2
|
name: package/irongraph.linux-arm64-gnu.node
|
|
3
|
-
size:
|
|
4
|
-
sha256:
|
|
3
|
+
size: 55481352 bytes
|
|
4
|
+
sha256: de4e192697928f6bb02fdf515a10ffd863592194e4804c9ee8d01af0be5da93e
|