A fast, reflection-free background task scheduler for .NET with source generators, EF Core/Redis persistence, cron execution, and a real-time dashboard.
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.
.NET developers building applications that require scheduled background tasks, such as web applications, microservices, or batch processing systems that need reliable job execution.
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.
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.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
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.
Includes a built-in SignalR dashboard for real-time job monitoring and management without paid add-ons, with screenshots available in the documentation.
Supports multi-node setups with Redis heartbeats and dead-node cleanup, enabling horizontal scaling and reliability through lock-based coordination.
Offers dual storage options via EF Core (PostgreSQL, SQL Server, SQLite, MySQL) or Redis, integrating directly with existing infrastructure without separate storage.
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.
Multi-node coordination requires Redis, adding infrastructure complexity and a potential single point of failure compared to simpler, in-memory schedulers.
Only supports specific databases through EF Core or Redis; projects using other data stores like MongoDB or Oracle would need custom workarounds.