5 replies

Need some suggestions about the DX

I'm probably in the minority here. But the DX for convex isn't awesome for bigger projects.

I'm coming from prisma and being able to do something like:

await prisma.damFile.update({
   where: {
      id: fileId,
   },
   data: {
      metaData: JSON.stringify(tags),
   },
});

await prisma.damFile.update({
   where: {
      id: fileId,
   },
   data: {
      metaData: JSON.stringify(tags),
   },
});

await prisma.damFile.update({
   where: {
      id: fileId,
   },
   data: {
      metaData: JSON.stringify(tags),
   },
});

await prisma.damFile.update({
   where: {
      id: fileId,
   },
   data: {
      metaData: JSON.stringify(tags),
   },
});

Anywhere in my codebase, for any table, with any filtering and any data and any methods is just liberating. I also don't need to think about any centralisation.

Compared to convex when I do have to think about this stuff.

And when I have encore, restate, rust, and a monorepo with multiple packages and domains all needing their own data accessibility. Now needing a centralised base. And with a codebase that's going to grow significantly bigger (when I get this poc done). I'm starting to grumble.

Unfortunately I couldn't get convex-ents to work. But now it's in maintenance mode so that's moot. Strage Error query2

Is there anything that's coming down the pike that is a departure from the status quo?

I love Convex due to it being rust and fitting nicely into my stack. But now I'm struggling due to the DX and getting it to fit in my codebase.

Any thoughts welcome!

Thanks!

Need some suggestions about the DX

Similar Threads

Similar Threads

Similar Threads