MongoDB
Use MongoDB when your Arc application needs document storage. Cratis.Arc.MongoDB handles collection injection and BSON conventions while letting you use the MongoDB driver directly. It is optional and does not require Chronicle.
Start with a read
Section titled “Start with a read”Follow getting started to install the package, configure a server/database, and activate your host. Keep that page as the canonical setup path rather than copying an incomplete bootstrap.
Model your documents
Section titled “Model your documents”- Concepts: store strongly typed values without wrapper documents.
- Serializers: understand BSON representations, including date precision and Guid formats.
- Naming policies: choose collection and member names before writing data.
- Class mapping: customize individual document types.
- Convention packs: apply and filter shared conventions.
- Geospatial types: store GeoJSON and construct driver query geometry.
Add live reads and tenancy
Section titled “Add live reads and tenancy”- Observe collections: per-collection change streams, lifetime, and errors.
- Watch multiple collections: shared database change streams and joined results.
- Tenancy: database naming and scope boundaries.
MongoDB observation is not an event log, and MongoDB persistence does not append Chronicle events. See the separate Chronicle integration if you intentionally add event sourcing.