Hey team I ve been playing around with
Hey team, I've been playing around with Convex and I'm seriously impressed. Our current stack is .NET Core-based API with a Remix (https://remix.run) frontend.
We have a few large, hairy workflows (for which we're using Temporal), but a lot of our app is quite simple, and desperately needs a better UI story. Is there a recommended pathway for migrating onto Convex piecemeal?
Other than the sync API, is there a way for our .NET backend to get access to data in Convex? Or do we need to move everything at once? Cheers 🙂
5 Replies
We are considering potentially adding a JS migration layer for a strangler-fig type approach.
Hi Mosen, you have a few options here. You can use Fivetran or Airbyte to get data from Convex into another system with some delay. You can use Convex mutations and queries to power the UI but schedule a Convex action to run immediately after each mutation to do a fetch notifying the .NET system of the change. You can power the UI with Convex HTTP endpoints instead of the sync WebSocket API if that's helpful for providing the same interface between the .NET server and Convex.
We haven't published a .NET client so it's hard to use the sync WebSocket protocol from C# but you can make HTTP requests to custom Convex HTTP endpoints.
Until your data is in Convex you won't see the benefits of live subscriptions, but while the .NET server owns the data double-writing by running a Convex mutation through a webhook would get Convex a copy of the data so reactive queries would work.
Awesome, thanks so much for the insight, @Tom
Would love to hear how it goes, this is coming up more lately so let us know if there are things that would make gradual migrations easier.
@Mosen 👋 sending you a DM