SurrealDB Stream #5: Live Queries with Tobie & Hugh

[@Cbon-xh3ry]

Any news regarding performance ?

[@PythonRussian]

Guys, how many live queries can be simultaneously? How many clients could connect to one DB and start live queries with different filters for each one of them?

[@SurrealDB]

From our simple tests, we can safely say Live Queries work well in the order of 100 open streams with constant traffic. This was tested with EchoDB which is a single writer. You will get much higher throughput on more capable storage engines such as RocksDB, TiKV, FoundationDB. We haven't yet fully tested the maximum load Live Queries can take, since we are already working on improving its design to allow better scalability. Hope this helps!

[@jafar1607]

What about the offline first scenario? I mean like mongo realm or pouchdb-counch db or power sync for superbase.

[@SurrealDB]

Hi! This is something we are looking into. It’s not ready yet, but the approaches we are looking into are using Change Feeds to sync databases and/or CRDTs.

[@vvalero44]

is it possible to embed this database in mobile devices as if it were sql lite3?

[@rushmorem]

Yes Victor it's possible to embed SurrealDB. Currently you can only do this with the Rust or WebAssembly library but we will be adding support for this in other languages over time.

[@RasmusSchultz]

Are live queries already available, or is this feature in development? I don't see it listed in the documentation.

[@SurrealDB]

Hey @RasmusSchultz, Live Queries is planned to be released with SurrealDB 1.0.0-beta.10. You can see more info on our Roadmap (surrealdb.com/roadmap) & Features (surrealdb.com/features) pages.

[@zz.onmywingss2889]

I already tried the live queries in release. It works very well. But I don't know how to manage the live query. When I create a live query, I have a UUID, I can kill live query by this UUID. But if I forget to kill this UUID, how can I can list all the current live query and clean it ???

[@SurrealDB]

Hi! Live queries will be visible in the INFO FOR DATABASE but if a client disconnects from a database, the associated Live Queries are automatically removed. KILL is used primarily for managing Live Queries while still connected. Hope that helps!

[@Rechdan]

Are we able to update a live query? For example change the value we are filtering in it?

[@SurrealDB]

Hey Nelson, Good Question! No you can’t update a LIVE query and update the filters / where condition, but you could just start a new live query with the new where condition, and close / KILL the old live query.

[@Rechdan]

@@SurrealDB that's what I had in mind, thank you 🙏🏻

[@gedw99]

If the live queries always have def out a sequence Izd then you could do catchup on the client. So you get CDC and Subscriptions from one system

[@SurrealDB]

Hey there, we initially designed Live Queries as a lower-overhead solution to streaming, while still providing more capabilities. Going forward we agree though, as the overhead from Change Feeds is acceptable and we can still provide the same capabilities. This will be addressed in an upcoming release.

[@oussamasethoum1665]

how can I secure the database, let's say I wanna deploy it on the client's end for a desktop app.

[@SurrealDB]

Hey Oussama, you'd have to consider injection attacks such as when using the HTTP endpoints in SurrealQL, as shown here: surrealdb.com/docs/integration/http#sql Hope this helps!