advice for migrating from pg+go+svelte
the below was copied from #general, as a Convex outage has drowned it in chat.
hello, I have a question regarding the backend functions. I might be looking at convex from a different perspective - as someone who uses mainly Go for backends both for side & work projects, is this something I'd have to drop, as as far as I understood convex is supposed to REPLACE my backend?
or should I regard these like pocketbase - a sort of.. preprocessor to db queries, which can be called from a frontend but if you're feeling like it you can also put a backend between it
given theres client libraries for things like python, is there some way to also opt in to using other non-js languages on the "backend" (through wasm or whatever)?
2 Replies
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!
Convex is definitely a complete backend. Like any database it can play whatever role you like in your stack, but it is built to replace your backend. The core can work with any language (for example there's an official Rust client), but there isn't a Go client yet. For Go and other languages that don't have explicit support, it's recommended to use OpenAPI to generate a typesafe client: https://docs.convex.dev/client/open-api