What Next?
You now understand the essential building blocks of Digital Alchemy Core:
- Services are plain functions that receive
TServiceParamsand return their public API - Modules wire services together;
LoadedModulesconnects the type system - Lifecycle hooks control when code runs —
PostConfig,Bootstrap,Ready - Configuration is declared per-module and validated at boot
- Libraries package services for reuse across applications
TestRunnerboots your real application in an isolated test environment
Reference — when you need the details​
| Topic | Reference page |
|---|---|
All CreateApplication options | CreateApplication |
All BootstrapOptions fields | Bootstrap Options |
TServiceParams full property list | TServiceParams |
| All 7 lifecycle hooks | Hooks |
| Lifecycle execution order and priorities | Execution Order |
| Config types, sourcing, and access | Config Overview |
| Logger, scheduler, event bus | Builtins |
TestRunner full API | TestRunner |
Guides — mental models​
| Question | Guide |
|---|---|
What exactly happens when I call bootstrap()? | Bootstrap Internals |
| Why DI? Why not just import everything? | Dependency Injection |
| How do I organize a real multi-service app? | Application Structure |
| How does config flow from env to my code? | Config and Environments |
| How should I approach testing? | Testing Strategies |
Advanced​
| Topic | Page |
|---|---|
| Async Local Storage and structured logging | Async Local Storage |
| Boot timing and performance metrics | Boot Metrics |
| Logger options, config sources, custom logger | Project Tuning |