Domain Driven Design Core
Description
The application of Domain Driven Design is not easy in general. The goal of this library is to be easy and well guided to develop ,. Not only ideas or DDD are used. CQRS and event sourcing are good suplements to this theory and it is a bit merged in this library.
Installation
This project has an automated deployment to pypi, so only is needed to use pip command:
>> pip install ddd-core
There is no external requirements for this library.
Usage
The use of this library is by inheritance. If you want to create a Value Object you only have to inherit from a Value class. If you want to have an aggregate, inherit from a Aggregate class, if a service from a Service class. It is planned to be widely docummented the behaviour is inherited from these classes.
I know composition is better than inheritance but a base class for each concept is the clearer way to implement DDD with OO programming.
Support
Send any suggestion to sruiz@indoorclima.com or salvador.ruiz.r@gmail.com. Any ideas or support is well recieved.
Roadmap
- Increment versioning when pushing
- Integrate with gitlab continuous integration to publish to pypi as library
- Improve coverage rate to > 96%
- Improve usage documentation with sphinx
- Upload to readthedocs
Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Authors and acknowledgment
For sure the ideas of Eric Evans and Domain Design Development are the base of this project to be used with python language. Without this seed it has not sensse
License
This is under LGPL lincense. You can use and modify this library.
Project status
It is used in projects developed currently by the company IndoorClima.
Metadata
Release files for ddd-core 0.1.3
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 |
|---|---|---|---|---|
| ddd_core-0.1.3.tar.gz | 6.8 kB | Without provenance | Details for ddd_core-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ddd_core-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for ddd_core-0.1.3-py3-none-any.whl |
Total release size: 14.6 kB
Release files / ddd_core-0.1.3.tar.gz
| Download URL | ddd_core-0.1.3.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
509b52b15670748cc84380183dde5ade7da08c53d9f8ef268a706c10b9eaa56a
|
|
BLAKE2b-256 checksum How to use checksums |
370b237e72b58dbadf02bbc24fdca51b721d32d1e6523585df06a77f5547c3ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.6 Linux/6.6.10-arch1-1
|
Release files / ddd_core-0.1.3-py3-none-any.whl
| Download URL | ddd_core-0.1.3-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ab74172945e6e271b2e4683d2ebf0a445b9dfe70ea4a570c87ca5ec72a4b950
|
|
BLAKE2b-256 checksum How to use checksums |
4e89abd0607bc8afb439e491b484efc541bc88733a1ba4093617da2e15b99aa3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.6 Linux/6.6.10-arch1-1
|
Security for ddd-core 0.1.3
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.