feat(serverless,dashboard): add Cron Functions

[QuiiBz]

About

Support back Cron functions!

[changeset-bot]

🦋 Changeset detected

Latest commit: c42af27

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@lagon/dashboard	Patch
@lagon/serverless	Patch
@lagon/docs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dashboard	❌ Failed (Inspect)			Jun 3, 2023 2:02pm

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)	Visit Preview		Jun 3, 2023 2:02pm
storybook	⬜️ Ignored (Inspect)	Visit Preview		Jun 3, 2023 2:02pm
www	⬜️ Ignored (Inspect)	Visit Preview		Jun 3, 2023 2:02pm

[akitaSummer]

@QuiiBz
Has our Cron Functions taken into account the distributed scenario of single-region multiple instances? I took a quick look at the code and it seems to be implemented using the Cronjob functionality provided by Tokio on the host machine. But in a distributed scenario, each instance will execute the Cron Functions, which may not be correct. Shouldn't we use RabbitMQ's delayed queue to implement Cron Functions?

[QuiiBz]

Has our Cron Functions taken into account the distributed scenario of single-region multiple instances?

No, for a few reasons:

• each region currently has a single instance running (yes, this isn't ideal, but I don't have the funds to do more than that, considering that Lagon doesn't have yet paying customers)
• it was a lot simpler and easier to do it using the simple way
• it works well for the current needs, the goal isn't to make every feature future-proof for growth

Shouldn't we use RabbitMQ's delayed queue to implement Cron Functions?

I'm not too familiar with RabbitMQ, but yeah there are a lot of ways to make this system "better" (more scalable, in the exchange of complexity). This isn't the priority at all right now but would be interesting to compare different solutions to find what we could use later to improve this system.