Collection Creation

Introduction

Like databases, collections are created implicitly on first insert. But you can also create them explicitly when you want to attach options up-front: schema validation, time-series settings, capped behavior, or a custom collation.

Understanding the topic

When to create explicitly:

• You want schema validation ($jsonSchema) from day one.
• You're building a time-series collection (IoT, metrics).
• You need a capped collection (fixed-size, FIFO eviction — great for logs).
• You want a collation (case-insensitive, locale-aware sort).

Syntax reference

// Implicit
db.events.insertOne({ type: "signup", at: new Date() });

// Explicit with validation
db.createCollection("orders", {
  validator: { $jsonSchema: { required: ["userId", "total"] } },
  validationLevel: "moderate"
});

// Time-series
db.createCollection("sensors", {
  timeseries: { timeField: "ts", metaField: "deviceId" }
});

Real-world use

Engineering teams often start implicit, then add validators once the document shape stabilizes. Time-series collections power industrial IoT pipelines at companies like Bosch and Toyota.

Best practices

• Start implicit, lock in validation once the shape is stable.
• Always use time-series collections for high-cardinality metrics.
• Capped collections are perfect for in-app log buffers.