Interest in a FaunaDB node?

I was recently made aware of the upcoming n8n which clearly is doing great. I created this ticket to poll for interest in a FaunaDB node. Let us know whether there are n8n users already familiar with FaunaDB who would love to see an integration or new users who would love to try out FaunaDB in combination with n8n by upvoting this feature request.

What is FaunaDB?
For people unfamiliar to FaunaDB, it’s a zero operations, global OLTP serverless database with strong consistency that offers some additional neat features like GraphQL, temporality, relations, etc. Since that’s a mouthful, let’s explain a few of the words in there:

  • OLTP: great for use cases with very frequent transactional writes and reads, e.g. social applications, financial apps, shops, etc. For an example, check out:

  • Zero operations and serverless: create an account, click a button and you have a database, create as many databases as you want in one account. FaunaDB is a cloud service where you don’t think about servers, operations, sharding or even configuring the available read/write operations. It’s seamlessly scalable and completely pay-as-you-go, you can even retrieve the cost of a query from the headers in the result. Serverless in this context means that you don’t care about servers.

  • Global: data is replicated globally providing your end users with low latencies, wherever your end user is located.

  • Strong consistency: inspired by a novel algorithm that allows the same level of consistency as Spanner without the need for special hardware to synchronize clocks. Therefore, an excellent choice for delicate transactions. The fourth article here explains that from a high perspective:

  • Relations,indexes, documents: relations are often abandoned in favor of scaling, FaunaDB offers scaling and consistency yet lets you express your data model with relations. Modeling is flexible with relations, powerful indexes and flexible documents.

  • GraphQL and FQL: you can start with GraphQL as well as the FaunaDB query language (FQL). The first gives you a familiar interface and you get started by simply uploading a schema. The second is an extremely powerful (yet slightly more verbose) language that excels at complex conditional transactions and was developed not to shoot yourself in the foot yet be as expressible as possible.

  • Temporality: you can query at a certain point in time and can leverage temporality to get changesets. Soon we will also provide push-based streams for UI redraw and push-based synchronization. These temporality features would probably make it easy and efficient to stream data into n8n, it sounds like a good match to me.