Refactor API/service boundaries and modularize frontend
This commit is contained in:
4
FAQ.md
4
FAQ.md
@@ -27,3 +27,7 @@ To start with a clean backend state, stop the app and remove the corresponding S
|
||||
## Does the backend read SQLite on every API call?
|
||||
|
||||
No. The backend loads state from SQLite once during startup into in-memory state and serves requests from memory. Successful state mutations are then written back to SQLite.
|
||||
|
||||
## Why do backend services use `*Command` types instead of API request DTOs?
|
||||
|
||||
Service workflows now consume service-layer command models (for example, `CreateCampaignCommand`) so endpoint transport contracts stay isolated in the API layer. This reduces coupling and keeps service code reusable when input shapes evolve at the HTTP boundary.
|
||||
|
||||
Reference in New Issue
Block a user