Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dymmond/asyncz
A python scheduler that simply does the job
https://github.com/dymmond/asyncz
api apscheduler async asyncio framework jobs pydantic python python-scheduler python3 scheduler task-scheduler tasks taskscheduler
Last synced: 4 days ago
JSON representation
A python scheduler that simply does the job
- Host: GitHub
- URL: https://github.com/dymmond/asyncz
- Owner: dymmond
- License: mit
- Created: 2022-12-15T11:05:23.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-11-18T13:59:14.000Z (about 1 month ago)
- Last Synced: 2024-12-14T18:48:11.619Z (8 days ago)
- Topics: api, apscheduler, async, asyncio, framework, jobs, pydantic, python, python-scheduler, python3, scheduler, task-scheduler, tasks, taskscheduler
- Language: Python
- Homepage: https://asyncz.dymmond.com
- Size: 422 KB
- Stars: 41
- Watchers: 3
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Security: SECURITY.md
Awesome Lists containing this project
README
# Asyncz
🚀 The scheduler that simply works. 🚀
---
**Documentation**: [https://asyncz.dymmond.com](https://asyncz.dymmond.com) 📚
**Source Code**: [https://github.com/dymmond/asyncz](https://github.com/dymmond/asyncz)
---
Asyncz is a scheduler for any ASGI application that needs to have those complicated scheduled operations with the
best of what pydantic can offer.
## Motivation
Nowadays using async frameworks with python is somewhat common and becoming even more mainstream. A lot of applications
usually need a complex stack of technologies to fullfil their needs and directly or indirectly, a scheduler.
There are great frameworks out there that do the task extremely well, the best example is APScheduler, which is where
Asyncz came from.
To be even more honest, Asyncz is a revamp of APScheduler. Without the APScheduler there is no Asyncz, so much that
even the APScheduler tests are used within asyncz. That is how great APScheduler is!
So what was the reason why recreating another similar version of APScheduler? Well, it is not entirely the same
thing. Asyncz was designed to work only with ASGI and AsyncIO as well as integrating pydantic and bring the modern
python into the table.
APScheduler is widely used by millions of python developers and Asyncz **does not aim to replace** it, instead
is a more focused and optimised solution for async and ASGI frameworks out there.
See the [vendors](./vendors/apscheduler/README.md) for more details.
## Logging
We all struggle with the logging and the configurations and with that in mind Asyncz comes with natice support
for loguru.
This will make the logging a lot easier to understand and clear to read.
## Async and ASGI
What does this mean? Well, Asyncz does not need to run inside any specific framework, actually you can use it
completely indepent from any framework as well as inside ASGI frameworks such as
[Esmerald](https://esmerald.dymmond.com), FastAPI, Starlette, Starlite, Quart... You can pick one and go for it.
Asyncz comes with special support to [Esmerald](https://esmerald.dymmond.com) for the simple reason that the author is
the same but it can be added more support. If you are interested in adding support to your favourite frameworks then
see the [contributing](https://asyncz.dymmond.com/contributing.md) section.
## Concepts
Like APScheduler, Asyncz also brings four kinds of components:
* [Schedulers](https://asyncz.dymmond.com/schedulers.md)
* [Triggers](https://asyncz.dymmond.com/triggers.md)
* [Stores](https://asyncz.dymmond.com/stores.md)
* [Executors](https://asyncz.dymmond.com/executors.md)
## Requirements
* Python 3.7+
Asyncz wouldn't be possible without two giants:
* APScheduler
* Pydantic
## Installation
```shell
$ pip install asyncz
```
## The right decisions
How do you know if you are choosing the right [scheduler](https://asyncz.dymmond.com/schedulers.md),
[triggers](https://asyncz.dymmond.com/triggers.md), [stores](https://asyncz.dymmond.com/stores.md)
and [executors](https://asyncz.dymmond.com/executors.md)?
Well, Asyncz is intentionally designed for specific systems and already helps you out with some of
those questions.
* **Schedulers** - Natively only supports the [AsyncIOScheduler](https://asyncz.dymmond.com/schedulers.md#asyncioscheduler).
* **Triggers** - Here it will depend of the periocidity of our tasks. Example:
* [CronTrigger](https://asyncz.dymmond.com/triggers.md#crontrigger) - UNIX like cron and gives you the same feeling as
scheduling a task on a native UNIX like based system.
* [DateTrigger](https://asyncz.dymmond.com/triggers.md#datetrigger) - When you need to run a task once on a specific
point of time.
* [IntervalTrigger](https://asyncz.dymmond.com/triggers.md#intervaltrigger) - When you need to run tasks in specific
intervals of time.
* [OrTrigger](https://asyncz.dymmond.com/triggers.md#ortrigger)/[AndTrigger](https://asyncz.dymmond.com/triggers.md#andtrigger) - If you would
like to combine more than one trigger (cron, interval and date) together.
* **Stores** - Natively only supports [redis](https://asyncz.dymmond.com/stores.md#redisstore),
[mongo](https://asyncz.dymmond.com/stores.md#mongodbstore) and [memory](https://asyncz.dymmond.com/stores.md#memorystore).
* **Executors** - Natively only supports [AsyncIOExecutor](https://asyncz.dymmond.com/executors.md#asyncioexecutor),
[ThreadPoolExecutor](https://asyncz.dymmond.com/executors.md#threadpoolexecutor) and
[ProcessPoolExecutor](https://asyncz.dymmond.com/executors.md#processpoolexecutor).
Sometimes having a lot of options makes the decision making very hard and Asyncz is intentionally
designed and driven to simplify and for specific use cases but is not limited to those. In every
section you have the option of uilding your own stores, executors, triggers and schedulers.
## Configuring the scheduler
Due its simplificy, Asyncz provides some ways of configuring the scheduler for you.
First way:
```python
from asyncz.schedulers.asyncio import AsyncIOScheduler
scheduler = AsyncIOScheduler()
```
Second way:
```python
from asyncz.schedulers import AsyncIOScheduler
scheduler = AsyncIOScheduler()
```
Initialize the rest of the application after the `scheduler` initialisation.
More [details](https://asyncz.dymmond.com/schedulers.md) can be found with more thorough explanations.
This is in simple terms and in a nutshell how to start with Asyncz quickly. For more information,
details and examples how to leverage Asyncz simply navigate through the documentation and have
fun 😁🎉.
## ASGI support
Asyncz currently supports ASGI, the [Esmerald framework](https://asyncz.dymmond.com/contrib/esmerald/)
and brings some batteries that are currently used by Esmerald and leveraging Asyncz.
```python
from asyncz.schedulers import AsyncIOScheduler
...
# handle_lifespan is optional, set to True if you don't want to pass it down because the underlying app doesn't support it
# this is true for django
application = AsyncIOScheduler().asgi(application, handle_lifespan=False)
# or more simple (please do not use both together)
application = AsyncIOScheduler().asgi()(application)
```
Using with lilya:
```python
from asyncz.schedulers import AsyncIOScheduler
# Lilya middleware doesn't pass lifespan events
app = AsyncIOScheduler().asgi(Lilya(
routes=[...],
))
```
Or manually:
```python
from asyncz.schedulers import AsyncIOScheduler
scheduler = AsyncIOScheduler()
app = Lilya(
routes=[...],
on_startup=[scheduler.start],
on_shutdown=[scheduler.shutdown],
)
```
## Contextmanager support
Use as sync contextmanager
```python
from asyncz.schedulers import AsyncIOScheduler
with AsyncIOScheduler() as scheduler:
...
```
Use as async contextmanager
```python
from asyncz.schedulers import AsyncIOScheduler
async with AsyncIOScheduler() as scheduler:
...
```
For using with lifespan of starlette:
```python
from asyncz.schedulers import AsyncIOScheduler
async lifespan(app):
with AsyncIOScheduler() as scheduler:
yield
# or yield a state
app = Starlette(
lifespan=lifespan,
)
```
## Security
You should use store encryption for security reasons.
All standard stores except MemoryStore support the environment variable `ASYNCZ_STORE_ENCRYPTION_KEY`.
If set and non-empty the hash of the value is used for AESGCM encrypting the elements before sending them
to the store.
This way store entries are encrypted and authentificated so there is no security hole.
This is highly recommended! Because if someone can inject store entries he can execute code.
## Sponsors
Currently there are no sponsors of **Asyncz** but you can financially help and support the author though
[GitHub sponsors](https://github.com/sponsors/tarsil) and become a **Special one** or a **Legend**.