Show HN: InstantDB – A Modern Firebase

Post by randomdata » Fri, Aug 23, 2024, 2:00 PM UTC

ashconnor wrote: post #46

jamest wrote: post #7

[Firebase founder] The thing I'm excited about w/Instant is the quad-fecta of offline + real-time + relational queries + open source. The amount of requests we had for relational queries was off-the-charts (and is a hard engineering problem), and, while the Firebase clients are OSS, I failed to open source a reference backend (a longer story). Good luck, Joe, Stopa and team!

I always assumed that an architectural decision had prevented relational queries in Firebase. It was jarring to find out that indexes are required for every combination of filters your app applies, but then you quickly realize that Firebase solves a particular problem and you're attempted to shoehorn into a problem-space better solved by something like Supabase. It's not too dissimilar to DynamoDB vs RDB.

Post by buf » Fri, Aug 23, 2024, 2:07 PM UTC

Post by sabbaticaldev » Fri, Aug 23, 2024, 2:17 PM UTC

aidos wrote: post #194

sabbaticaldev wrote: post #184

Earlier quoted context omitted.

A thenable API from save() could remove the need of a explicit tx management which is a worse devEx

I’m not quite seeing what you mean. What you mind redoing the example above for my benefit? We have controllers that all the users actions are funnelled through. The top level functions in there are wrapped in transactions so in practice it’s not something you manually wrangle.

  author.save()
 .then(() => {
    const article = new Article(db);
    article.name = "New name";
    article.author = author;
    return article.save(); // could be used to chain the next save
 })
 .then(() => {
    console.log("Both author and article saved successfully.");
 })
 .catch((error) => {
    console.error("rollback, no changes");
 });

Post by ochiba » Fri, Aug 23, 2024, 2:19 PM UTC

satvikpendem wrote: post #167

ochiba wrote: post #65

Earlier quoted context omitted.

Co-founder of PowerSync here. Would love to hear what you would like to see improved in PowerSync :) Thanks!

ElectricSQL before their announced rewrite worked fully offline and could sync when the clients became online again. Now, that functionality with their rewrite is somewhat removed, as they expect you to handle clientside writes by yourself, which is what I believe PowerSync does as well, am I correct in that understanding? If I wanted a fully offline clientside database that could then sync to all the other clients w…

Post by h4ny » Fri, Aug 23, 2024, 3:02 PM UTC