Nicolas
Nicolas2y ago

Scheduling, AWS, and form validation

Hi All, new to Convex here, building out a multi-tenant app to interface with custom hardware, and I have been using SST so far, but this platform looks like a game changer for building apps in a super easy way, and should help me get to production sooner! I just had a couple of questions that I couldn't see a direct answer for on the docs: 1. Is it possible to make a schedule that will run at a specific timestamp, dynamically, based on the user input? I noticed the runAt function, but wasn't sure if that can be called dynamically with another function/action, or if that's effectively a IaC construct. For instance, a user will select a date-time using a calendar / time UI on the front-end, and then the backend will need to create a schedule for some action to run based on that date-time submittal. 2. Are there any limits to how many schedules can be enabled at a time? Or how many schedules can be queued to run? What is the pricing around this? 3. I am making a mult-tenant app, and customers may upgrade to higher tier to have a white-labeled app with their own custom domain, is it possible to have custom domains set for the same app to handle multi-tenant white-labeling? 4. In terms of hosting, I would like to use AWS with CDN + AWS Certificate Manager for handling domains (this is related to the question above), is there documentation surrounding use AWS for hosting? 5. Is there documentation that showcases using the schema definitions to implement form validation with useForm? 6. Do we have the ability to backup our data to an S3 bucket, for instance? 7. How long has Convex been around? Is there a roadmap showcasing upcoming features and development plans? Thank you!
7 Replies
ballingt
ballingt2y ago
Hi! To answer a few of these: Yep, ctx.runAt scheduling is totally dynamic. Cron jobs are not, they're configuration as code like you describe. No limits on the number if jobs scheduled, they just count as function executions. For custom domain whitelabeling: the Convex domain like https://happy-otter-123.convex.cloud isn't visible to end users unless they open the network tab, so it's not clear to me what you'd want to whitelabel. Convex doesn't host your frontend, so you can use as many domains and even separate webapps as you want with the same Convex backend. Does this answer make sense @Nicolas? For hosting you host your frontend however you like, eg an AWS CDN, and Convex powers the backend.
Nicolas
NicolasOP2y ago
Oh ok I got it now, this makes sense! Yes everything here makes sense, thank you for the quick response!
jamwt
jamwt2y ago
Are there any limits to how many schedules can be enabled at a time? Or how many schedules can be queued to run? What is the pricing around this?
Yes, there is a limit to how many things can be scheduled, but it is quite high. Pricing is only really charged per function invocation (or action GB-second), not just for scheduling
documentation surrounding use AWS for hosting
Nope! But we can look into this. Mostly folks use vercel or netlify for hosting right now, but should be pretty straightforward with AWS as well
Do we have the ability to backup our data to an S3 bucket, for instance?
Yes, there are two ways to do this right now. (1) in the dashboard, you can download database snapshots; (2) you can set up a fivetran streaming export, which keep an up to date stream of your dataset to lots of different formats, including parquet-on-s3
How long has Convex been around? Is there a roadmap showcasing upcoming features and development plans?
Convex has been around for about 2.5 years. We don't have a public place we maintain a roadmap, but @james , our CTO, tends to drop an update once or twice a quarter with our product development plans for the next 6-10 weeks
Nicolas
NicolasOP2y ago
Thanks for the answers! That's awesome! Super excited to start trying out Convex, I can tell a lot of thought and work went into this. I haven't seen another service that is this easy to use for infrastructure management and end to end type safety before, and by the looks of it, I can see this thing taking off like wildfire.
jamwt
jamwt2y ago
thanks so much! it's definitely a slightly different way to think about building backends than most folks are used to, but people do tend to really like it once they've got the concepts down
Nicolas
NicolasOP2y ago
That's great for me, I honestly prefer a strongly opinionated way of doings things as I am pretty new to dev ops and infrastructure overall; I'd rather just do everything the way the experts and those with experience recommend lol
jamwt
jamwt2y ago
great. well, while it's always nice when people who have a deep infra background appreciate convex, in many ways it's even more important to make sure folks who haven't really much infra before can build their backends with ease + delight as well so keep the feedback coming

Did you find this page helpful?