How do I schedule a cron job with TickerQ?

Use the TimeTickerManager to add a cron-based TimeTickerEntity. The README shows basic scheduling, and the documentation details cron syntax support for recurring jobs with examples.

TickerQ vs Hangfire which is better for .NET?

TickerQ excels in AOT and reflection-free environments with source generation, while Hangfire has a more mature ecosystem and broader community. Choose TickerQ for performance optimization or Hangfire for feature richness and ease of adoption.

Can TickerQ run without a database?

No, TickerQ requires persistence via EF Core or Redis for job storage. For purely in-memory scheduling, you'd need to use Redis or a database, as it doesn't support volatile storage alone.

How to set up the TickerQ dashboard in my app?

Add the TickerQ.Dashboard package, register services with AddTickerQ(), and use app.UseTickerQ() in your Startup. The dashboard is served automatically via SignalR for real-time monitoring.

Does TickerQ support SQLite for local development?

Yes, TickerQ.EntityFrameworkCore supports SQLite along with PostgreSQL, SQL Server, and MySQL, making it suitable for development and testing environments.

How to handle job retries and failures in TickerQ?

Configure retry policies when scheduling jobs using TimeTickerEntity. The features mention configurable retry with backoff, and the documentation provides specifics on setting up retry logic for robust error handling.

Open-Awesome

TickerQ

NOASSERTIONC#v10.3.0

A fast, reflection-free background task scheduler for .NET with source generators, EF Core/Redis persistence, cron execution, and a real-time dashboard.

Visit Website GitHub

3.6k stars218 forks0 contributors

What is TickerQ?

TickerQ is a background task scheduler for .NET applications that enables developers to schedule and execute jobs using time-based or cron-based triggers. It solves the problem of reliable job execution with persistence, distributed coordination, and real-time monitoring built directly into the framework.

Target Audience

.NET developers building applications that require scheduled background tasks, such as web applications, microservices, or batch processing systems that need reliable job execution.

Value Proposition

Developers choose TickerQ for its reflection-free, source-generated architecture that ensures maximum performance and AOT readiness, combined with built-in persistence options and a real-time dashboard that eliminates the need for third-party monitoring tools.

Overview

TickerQ is a fast, reflection-free background task scheduler for .NET built with source generators, EF Core integration, cron + time-based execution, and a real-time dashboard.

Use Cases

Best For

Scheduling recurring maintenance tasks in .NET web applications
Building distributed job processing systems with multiple worker nodes
Implementing cron-like job scheduling within .NET microservices
Creating background task queues with persistence to SQL databases or Redis
Developing applications requiring real-time monitoring of job execution status
Optimizing .NET applications for AOT compilation with reflection-free job scheduling

Not Ideal For

Projects requiring dynamic job registration at runtime without recompilation
Teams using non-.NET frameworks or languages
Applications needing only simple, in-memory task scheduling without persistence
Environments without Redis for distributed coordination

Pros & Cons

Pros

AOT-Ready Performance

Uses source generators for compile-time function registration, eliminating runtime reflection and ensuring full trimmability for AOT compilation, as highlighted in the 'Zero reflection, AOT ready' feature.

Integrated Monitoring Dashboard

Includes a built-in SignalR dashboard for real-time job monitoring and management without paid add-ons, with screenshots available in the documentation.

Distributed Coordination

Supports multi-node setups with Redis heartbeats and dead-node cleanup, enabling horizontal scaling and reliability through lock-based coordination.

Flexible Persistence

Offers dual storage options via EF Core (PostgreSQL, SQL Server, SQLite, MySQL) or Redis, integrating directly with existing infrastructure without separate storage.

Cons

Package Version Lock-in

All TickerQ packages must be updated to the same version, complicating dependency management and increasing the risk of conflicts, as noted in the package documentation.

Redis Dependency for Scaling

Multi-node coordination requires Redis, adding infrastructure complexity and a potential single point of failure compared to simpler, in-memory schedulers.

Limited Database Support

Only supports specific databases through EF Core or Redis; projects using other data stores like MongoDB or Oracle would need custom workarounds.

Frequently Asked Questions

Related Projects

QuartzNet

Quartz Enterprise Scheduler .NET

Stars7,093

Forks1,706

Last commit4 days ago

Workflow Core

Lightweight workflow engine for .NET Standard

Stars5,935

Forks1,261

Last commit2 days ago

DurableTask

Durable Task Framework allows users to write long running persistent workflows in C# using the async/await capabilities.

Stars1,742

Forks338

Last commit3 days ago

NCrontab

Crontab for .NET

Stars987

Forks141

Last commit11 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub