Paul•2mo ago

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),
   },
});

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. https://discord.com/channels/1019350475847499849/1230233206893314111/1230233206893314111 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!

4 Replies

Convex Bot•2mo ago

Thanks for posting in <#1088161997662724167>. Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets. - Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.) - Use search.convex.dev to search Docs, Stack, and Discord all at once. - Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI. - Avoid tagging staff unless specifically instructed. Thank you!

jamwt•2mo ago

Am I understanding you correctly, you essentially want higher-level constructs ala ents? if so, ents still exists, is an open source project, and we're open to PRs. and we're intending to incorporate some parts of ents (join ergnomics, maybe?) into the base level convex v2 API. but just like SQL has ORMs, convex will always have some even higher-level APIs build on top of the foundational primitives. and so if our API is not high level enough for your taste, you can write or use a layer that provides the expressive semantics you like in particular

PaulOP•2mo ago

Do you know offhand links to docs or stack articles which discuss how the database works with respect to queries/mutations etc with a view or writing a layer? Ok found: https://stack.convex.dev/how-convex-works digging into that 😄

jamwt•2mo ago

ent's implementation itself is really good as well, as @Michal Srb knows the ins and outs of convex intimately

Need some suggestions about the DX

Did you find this page helpful?