Spaces:
Sleeping
Sleeping
|
Download doc/planning/micro-modules.md from AZILS/puter-deploy: direct link, hf CLI and curl.
- Browser
- Download file 597 Bytes
-
https://huggingface.co/spaces/AZILS/puter-deploy/resolve/main/doc/planning/micro-modules.md
- Command line
-
hf download hf://spaces/AZILS/puter-deploy/doc/planning/micro-modules.md
-
curl -L -o micro-modules.md https://huggingface.co/spaces/AZILS/puter-deploy/resolve/main/doc/planning/micro-modules.md
597 Bytes
| # Micro Modules | |
| **CoreModule** has a large number of services. Each service handles | |
| a general concern, like "notifications", but increasing this granularity | |
| a little put more could allow a lot more code re-use. | |
| One specific example that comes to mind is services that provide | |
| CRUD operations for a database table. The **EntityStoreService** can | |
| be used for a lot of these even though right now it's specifically | |
| used for drivers. Having a common class of service like this can also | |
| allow quickly configuring the equivalent service for providing those | |
| CRUD operations through an API. | |