MongoDB Academy · レッスン

スキーマ設計の意思決定フレームワーク

クエリパターン、書き込み頻度、ドキュメントの増大などのチェックリストを使い、どのドメインでも埋め込みと参照のどちらを選ぶか判断します。

レッスン 4/413 ステップ

「スキーマ設計の意思決定フレームワーク」はCoddyKit上の無料MongoDB Academyレッスンです。これはレッスン4/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはMongoDB Academy学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 MongoDB Academyコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Why a Decision Framework Matters

MongoDB's schema flexibility is powerful but can lead to analysis paralysis. Should you embed or reference? When is the choice not obvious? A structured decision framework replaces guesswork with a repeatable checklist. By asking the same questions about query patterns, write frequency, and document growth, you can arrive at the right schema for any domain—consistently.

Step 1: Identify Query Patterns

Start by listing the most frequent read queries your application makes. Ask: do these queries always need the parent and children together, or are children queried independently? If child data is almost always fetched with its parent, embedding eliminates a round trip. If children are frequently queried, sorted, or filtered on their own, referencing keeps queries simple and indexes focused.

Step 2: Estimate Data Size and Growth

For every potential array or nested structure, ask: how many elements will this have at steady state, and can it grow without bound? Use rough business rules: a user rarely has more than 5 addresses (embed), but can write thousands of reviews (reference). Anything with an unbounded or unknown upper limit is a candidate for a separate collection.

Step 3: Evaluate Write Frequency

Consider how often the child data is written compared to the parent. Embedding means every child update rewrites the parent document, triggering a storage move if the document grows. If children are updated very frequently and independently of the parent, the overhead of rewriting the parent each time favours referencing—child documents update in place without touching the parent at all.

Step 4: Check for Data Sharing

Ask whether the child data is owned by one parent or shared across multiple parents. An address is owned by a single user—safe to embed. A product in a catalogue is referenced by potentially thousands of orders—it must be in its own collection to avoid duplication and stale data. Shared data should always be referenced, never embedded.

Step 5: Assess Atomicity Requirements

MongoDB guarantees atomic writes at the document level for free—no transactions needed. If you need to update a parent and its children atomically, embedding keeps both in the same document so any update is atomic by default. If you reference across two collections and need atomicity, you must use a multi-document transaction, which adds latency and complexity.

The Framework Decision Table

Apply these rules in order:

Children always fetched with parent + small count + owned by parent: EMBED
Children queried independently or shared: REFERENCE
Children can grow without bound: REFERENCE (or bucket pattern)
Atomic update required across parent + children: EMBED (or transaction)
Write frequency of children high relative to parent: REFERENCE

If multiple rules conflict, referencing is the safer default.

Example: E-Commerce Order Schema

Apply the framework to an order in an e-commerce system. Line items: always fetched with order, small count (under 50), owned by order → embed. Shipping address: snapshot at order time, never shared → embed. Customer: shared across thousands of orders → reference. Product catalogue: shared across orders, updated independently → reference.

db.orders.insertOne({
  _id: ObjectId(),
  customerId: ObjectId('c1'),        // reference — shared data
  shippingAddress: {                 // embed — point-in-time snapshot
    street: '123 Maple St',
    city: 'Austin'
  },
  items: [                           // embed — small, owned by order
    { productId: ObjectId('p1'), qty: 2, price: 19.99, name: 'Widget' }
  ]
});

Example: Social Media Schema

Apply the framework to a social media post. Post author: shared across posts → reference. Post body and metadata: owned by post, small → embed. Likes (count only): numeric field → embed as a counter. Comments: potentially thousands, queried and paginated independently → reference in a separate comments collection.

db.posts.insertOne({
  _id: ObjectId(),
  authorId: ObjectId('u1'),           // reference
  title: 'Why MongoDB rocks',
  body: '<p>Because documents...</p>',
  tags: ['mongodb', 'nosql'],         // embed — small, owned
  likesCount: 0,                      // embed — simple counter
  createdAt: new Date()
  // comments live in db.comments, NOT embedded here
});

Evolving Your Schema Over Time

The right schema at launch may not be the right schema at scale. Start with the simplest correct design. If you later discover that an embedded array is growing too large, migrate it to a separate collection. MongoDB's flexible schema makes incremental evolution possible—you can write new documents in the new shape while keeping old ones, then backfill with a migration script.

Documenting Your Schema Decisions

Write down the reasoning behind each schema choice while it is fresh. A comment in a Mongoose schema file or a short design document explaining why items are embedded but customerId is referenced pays enormous dividends when a new engineer joins or when you revisit the schema six months later. Schema design is a deliberate act, not an accident.

const orderSchema = new mongoose.Schema({
  customerId: { type: mongoose.Schema.Types.ObjectId, ref: 'Customer' }, // reference: shared
  shippingAddress: addressSchema,  // embed: point-in-time snapshot
  items: [lineItemSchema],         // embed: small, always with order
  status: { type: String, enum: ['pending', 'shipped', 'delivered'] },
  createdAt: { type: Date, default: Date.now }
});

Quick Check

Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.

対話的なレッスンで答える

Lesson Recap

In this lesson you learned: the five-step decision framework covers query patterns, data size, write frequency, sharing, and atomicity, shared data always belongs in a separate referenced collection, and schema decisions should be documented alongside the code. Next up we explore schema validation with JSON Schema to enforce data quality in MongoDB collections.

無料で開始

AI チューターと学ぶ JavaScript — 無料

ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。

コース: 30
レッスン: 120

無料で学習を始めるコース全体を表示

よくある質問

「スキーマ設計の意思決定フレームワーク」レッスンは無料ですか？

はい。「スキーマ設計の意思決定フレームワーク」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、MongoDB Academyコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 MongoDB Academyコースには全4レッスンが含まれています。

「スキーマ設計の意思決定フレームワーク」で何を学びますか？

クエリパターン、書き込み頻度、ドキュメントの増大などのチェックリストを使い、どのドメインでも埋め込みと参照のどちらを選ぶか判断します。ブラウザで直接実行するハンズオンコードでMongoDB Academyを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

MongoDB Academyを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのMongoDB Academyは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン4/4です。

「スキーマ設計の意思決定フレームワーク」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このMongoDB Academyレッスンでコードを書いて実行できますか？

はい。すべてのMongoDB Academyレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← MongoDB Academyに戻る