Durable Call: Durable Local and Remote Function Calls
Durable call is a library for implementing durable functions from fragile functions.
A function is said to be fragile if any of the following conditions are true: a) the function may fail intermittently, b) the function call has side effects, and thus for a given input it should only be run once.
A durable function is a fault tolerant and idempotent version of a fragile function. This fault tolerance and idempotency is implemented by the runtime. When a durable function is called, the runtime system first saves the parameters of the function call onto a file on disk. Next it repeatedly tries to call the function until it is able to execute it. Once the function has been executed, the result is also saved onto a file on disk. If the function is called in the future with the same arguments, the system will just return the saved result from the previous invocation.
Durable function call persists across process invocations. If a durable function call is initiated, and the process dies before it has been completed, the runtime with continue to execute it if the process is restarted.
Metadata
Release files for durable-call 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| durable-call-0.1.0.tar.gz | 7.0 kB | Without provenance | Details for durable-call-0.1.0.tar.gz |
Release files / durable-call-0.1.0.tar.gz
| Download URL | durable-call-0.1.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbe0bd29e8a7faae83ad26c03390c826028bb1db08a4c95bd32cd55759e428ae
|
|
BLAKE2b-256 checksum How to use checksums |
a979522f19925db3a8f01efa30f643932fd881f127317e3592ea0c0c07ef7ea8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for durable-call 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.