Convex vs. Firebase

Post by shhsshs » Wed, Jun 22, 2022, 12:18 PM UTC

TekMol wrote: post #33

habosa wrote: post #15

Earlier quoted context omitted.

A few points here: 1) That’s a JOIN and Firestore is not unique among NoSQL databases for being bad at it. 2) That’s the code you’d use in a web browser to load Firestore data. That code also handles all of the API and Authentication code you’d normally put in front of another DB. It’s serverless. So that is a fully functional snippet, your SQL example needs an API layer and frontend deserialization code. 3) It does…

2: The code does not handle authentification. The code literally just says "Give me this, give me that...". 3: It is still a "a client-server http roundtrip" for every query. It does not open and close the http connection every time. But it sends a "GET / HTTP ..." request for every query. With hostname, accepted formats, encodings etc.

Post by jmkni » Wed, Jun 22, 2022, 12:49 PM UTC

_vvhw wrote: post #30

The founders of Convex are some of the most talented developers I know. The CTO worked with Turing-award winner Barbara Liskov on Viewstamped Replication Revisited [1], the revision of the pioneering consensus protocol, and later the founding team pulled off the migration of Dropbox from S3 to their own custom storage stack called Magic Pocket [2]. The deterministic simulation testing techniques [3] they used to deve…

Post by jitl » Wed, Jun 22, 2022, 1:14 PM UTC

james_cowling wrote: post #5

rockwotj wrote: post #4

So the reactivity here is based on smart polling? > Later on, if any mutation inserts, updates, or deletes a record that overlaps with the read set, Convex knows it needs to recompute the listMessages query. If the result of listMessages changes, the new value is synced to the client and the component rerenders. FWIW Firestore is able to send incremental updates and not just rerun the query when data changes. There i…

I'm not sure what your definition of smart polling is but there is no polling going on here - the query only reruns when the data dependencies change server-side due to a subsequent mutation. Another key distinction is that "query" here doesn't refer to a database read, it could be a complex function containing multiple reads, relatively-arbitrary compute, etc.

Post by lucideer » Wed, Jun 22, 2022, 1:37 PM UTC

TekMol wrote: post #6

According to the article, this is how you load messages and their users from a DB via Firebase: const querySnapshot = await getDocs(collection(db, "messages")); const userSnapshots = await Promise.all( querySnapshot.docs().map(async messageSnapshot => { return await getDoc(docSnapshot.data().creator); }) ); Phew! Thanks, but no. Never. I will keep doing it server side: $messages = DB::select( 'SELECT * FROM messages…

    const userSnapshots = await Promise.all(
        getDocs(collection(db, "messages")).then(
            docs => docs().map(snapshot => getDoc(snapshot).data().creator)
        )
    )

Post by uptown » Wed, Jun 22, 2022, 1:53 PM UTC