Go to file
cuddle-please 788f64cc3b
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/pr Build is passing
chore(release): 0.3.0
2024-08-07 13:53:40 +00:00
crates/mad feat: add add_fn to execute immediate lambdas 2024-08-07 15:53:04 +02:00
.drone.yml feat: add basic 2024-08-06 22:22:46 +02:00
.gitignore feat: add basic 2024-08-06 22:22:46 +02:00
Cargo.lock feat: add add_fn to execute immediate lambdas 2024-08-07 15:53:04 +02:00
Cargo.toml chore(release): 0.3.0 2024-08-07 13:53:40 +00:00
CHANGELOG.md chore(release): 0.3.0 2024-08-07 13:53:40 +00:00
cuddle.yaml feat: add basic 2024-08-06 22:22:46 +02:00
README.md docs: add a small readme 2024-08-07 12:08:21 +02:00

MAD

Mad is a life-cycle manager for long running rust operations.

  • Webservers
  • Queue bindings
  • gRPC servers etc
  • Cron runners

It is supposed to be the main thing the application runs, and everything from it is spawned and managed by it.

struct WaitServer {}

#[async_trait]
impl Component for WaitServer {
    fn name(&self) -> Option<String> {
        Some("NeverEndingRun".into())
    }

    async fn run(&self, cancellation: CancellationToken) -> Result<(), mad::MadError> {
        let millis_wait = rand::thread_rng().gen_range(50..1000);

        // Simulates a server running for some time. Is normally supposed to be futures blocking indefinitely
        tokio::time::sleep(std::time::Duration::from_millis(millis_wait)).await;

        Ok(())
    }
}

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    Mad::builder()
        .add(WaitServer {})
        .add(WaitServer {})
        .add(WaitServer {})
        .run()
        .await?;

    Ok(())
}