BLUMYCELIUM: Async micro-services, 100% in python from Bluwr
This tool os provided for free by [bluwr.com](https://bluwr.com). We are building a 100% text based publication platform. A calm space free of any addictive feature.
- Here are a few things that you can do to support us:
Register for early access on [bluwr.com](https://bluwr.com)
Buy some awesoms merch on our [store](https://store.bluwr.com)
Follow us on social media [instagram](https://www.instagram.com/bluwr_official/), [twitter](https://twitter.com/bluwr_official), [linkedin](https://www.linkedin.com/company/bluwr)
Machine Elf <- Mycelium -> Machine Elf
PLEASE NOTE: This documentation is a work in progress
BLUMYCELIUM is our tool for arm’s-length microservices management and orchestration. It allows for the splitting of a monolithic application into several small parts that run asynchronously in the same environment and can be tested separately. BLUMYCELIUM was developed to be easy to learn and does not require more than python knowledge to achieve results that would normally be implemented using more complex DevOps orchestration tools mediated through REST APIs. To achieve this, Blumycellium relies heavily on python introspection capabilities to follow the flow of variable updates and transparently derives execution and orchestration graphs. By allowing services to be separate programs BLUMYCELIUM applications can also bypass the python GIL. BLUMYCELIUM also remembers the source code of all tasks as well as tracebacks for all exceptions for easy debugging. BLUMYCELIUM is implemented using the flexible multimodal ArangoDB database for storing what we call the: Mycelium. The repository of everything needed for variable execution graphs, source codes, orchestrations and failure reporting.
BLUMYCELIUM allows you to write complex microservice orchestration all in python. You can divide a complex application into many smaller parts that can be tested independtly and ran asynchronously. These smaller parts are agents called Machine Elves and the Mycelium is the database they use to communicate.
Readthedocs documentation
We provide a full documentation [here](https://blumycelium.readthedocs.io/en/latest/index.html) (work in progress).
Feedback
If you have any suggestions about features or feedback about the documentation please open github issues.
1 maintainer
Metadata
1 maintainer
Release files for blumycelium 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 |
|---|---|---|---|---|
| blumycelium-0.1.0.tar.gz | 20.7 kB | Without provenance | Details for blumycelium-0.1.0.tar.gz |
Release files / blumycelium-0.1.0.tar.gz
| Download URL | blumycelium-0.1.0.tar.gz |
|---|---|
| Size | 20.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d78f5f402d8d05f1b8af60b4de902bc3c4c5e46cf083f64b0f74853fb54e33bc
|
|
BLAKE2b-256 checksum How to use checksums |
a70ea5f029773f3f03916d359ce6ff272bc926e998788a7fb32eebf38be0a0b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.8.5
|
Security for blumycelium 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.
