tigris VS relic

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Sounds like you might be interested in the Tigris preview:

- https://www.tigrisdata.com/

- https://benhoyt.com/writings/flyio-and-tigris/ (discussed here: https://news.ycombinator.com/item?id=39360870)

- https://fly.io/docs/reference/tigris/

Tigris: an open source Serverless NoSQL Database and Search platform

Tigris is an open source serverless NoSQL database and search platform. If you have any questions, or you'd like to contribute to the Tigris open source project.

To try the Tigirs database with express app, visit: https://www.tigrisdata.com/ Signup, and create a test app. It'll provide a command set of npm. Create an express app using it and you'll be able to explore the codebase and queries.

Tigris(https://github.com/tigrisdata/tigris) is one of the supported FerretDB backends and Tigris is backed by FoundationDB, so you can still have the Mongo interface with the reliability and scaling of FDB if that's what you're looking for

Based on the feedback in this thread I have updated the headline on the website to make it about what the product is and moved down the "MongoDB alternative" part. I hope it is more clearer now: https://www.tigrisdata.com/

I've been tooling around with "Tuple Database", which claims to be FoundationDB for the frontend (by the original dev of Notion).

https://github.com/ccorcos/tuple-database/

I have found it conceptually similar to Relic or Datascript, but with strong preformance guarantees - something Relic considers a potential issue. It also solves the problem of using reactive queries to trigger things like popups and fullscreen requests, which must be run in the same event loop as user input.

https://github.com/wotbrew/relic

As an alternative to datascript you might be interested to try https://github.com/wotbrew/relic which does materialized views of queries with incremental maintenance.

I came across this after seeing relic[0] submitted the other day and thought it was pretty interesting.

I've been into CRDTs for a while and have started wondering about generic mechanisms for distributed data. This lead me to read a lot more about the Relational Model of data and eventually to the Event Calculus.

What's interesting to me is that these things end up feeling a lot like CRDTs[1] or Event Sourcing. I haven't quite finished pulling on these threads but the relic link was a timely read considering!

I really liked the first half of this paper and the Authors categorization of complexity. However the second half fell a bit short for me. It seems they made the same mistake as many other people (SQL != Relational) and their idea of Feeders and Observers seems a bit more like an escape hatch than an elegant method for interfacing with the outside would.

[0] https://github.com/wotbrew/relic

I have recently cut the first alpha release of relic that I'm happy to share: https://github.com/wotbrew/relic.