lentil/rhizome-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: lentil:main
Branches Tags
lentil:main
lentil:feature/docker-orchestrator-tests
lentil:pr-1-feedback
lentil:claude_code_work
..
compare: lentil:pr-1-feedback
Branches Tags
lentil:feature/docker-orchestrator-tests
lentil:main
lentil:pr-1-feedback
lentil:claude_code_work

No commits in common. "main" and "pr-1-feedback" have entirely different histories.
main ... pr-1-feedb

1 changed files with 19 additions and 17 deletions
Show Stats Expand all files Collapse all files

36
README.md
View File

@ -1,5 +1,23 @@
See [spec.md](spec.md) for additional specification details about this project. See [spec.md](spec.md) for additional specification details about this project.
# Concepts
| | Implemented | Notes |
| ------------- | ----------- | ------------------------------------------------------------------------ |
| Peering | Yes | Implemented with ZeroMQ and/or Libp2p. Libp2p solves more problems. |
| Schemas | Not really | Currently very thin layer allowing TypedCollections |
| Relationships | No | Supporting relational algebra among domain entities |
| Views | Yes | Lossless: Map the `targetContext`s as properties of domain entities. |
| | | Lossy: Use a delta filter and a resolver function to produce a view. |
| | | Currently using functions rather than JSON-Logic expressions. |
| Functions | No | Arbitrary subscribers to delta stream (that can also emit deltas?) |
| Tests | Yes | We are set up to run unit tests and multi-node tests |
| Identity | Sort of | We have an identity service via Libp2p |
| Contexts | No | Each context may involve different lossy functions and delta filters |
| HTTP API | Yes | Basic peering info and entity CRUD |
If we express views and filter rules as JSON-Logic, we can easily include them in records.
# Development / Demo # Development / Demo
## Setup ## Setup
@ -138,23 +156,7 @@ EOF
curl -s -X PUT -H 'content-type:application/json' -d @/tmp/user.json http://localhost:3000/api/user | jq curl -s -X PUT -H 'content-type:application/json' -d @/tmp/user.json http://localhost:3000/api/user | jq
``` ```
# Concepts # More About Concepts
| | Implemented | Notes |
| ------------- | ----------- | ------------------------------------------------------------------------ |
| Peering | Yes | Implemented with ZeroMQ and/or Libp2p. Libp2p solves more problems. |
| Schemas | Not really | Currently very thin layer allowing TypedCollections |
| Relationships | No | Supporting relational algebra among domain entities |
| Views | Yes | Lossless: Map the `targetContext`s as properties of domain entities. |
| | | Lossy: Use a delta filter and a resolver function to produce a view. |
| | | Currently using functions rather than JSON-Logic expressions. |
| Functions | No | Arbitrary subscribers to delta stream (that can also emit deltas?) |
| Tests | Yes | We are set up to run unit tests and multi-node tests |
| Identity | Sort of | We have an identity service via Libp2p |
| Contexts | No | Each context may involve different lossy functions and delta filters |
| HTTP API | Yes | Basic peering info and entity CRUD |
If we express views and filter rules as JSON-Logic, we can easily include them in records.
## Clocks? ## Clocks?