- Object storage centric. In its final version Triplox should simply need a single (or likely two) S3 bucket(s) for deployment.
- The Datomic data model and API as main inspiration.
- A client/server architecture.
- Incremental Datalog queries. You can dynamically subscribe and unsubscribe from live Datalog queries. This is the most experimental part of Triplox and will need more effort to scale. Standard connectives (`and`, `or`, `not`) are already supported. You can find an intro here: https://triplox.xyz/incremental-queries/overview/.
The incremental query angle is likely the most interesting aspect for people considering such a solution. If you have an incremental Datalog problem or are working on sync engines, Triplox might be of interest.
Website: https://triplox.xyz/
panick21_•2m ago
There was a team that did something like this, I saw a talk about it once. But I think they did in JS with Datomic in browser that somebody wrote. I might update this comment later with the relevant links.
But its really cool idea and I think very useful for some applications.