Préférences de lecture : répartir la charge de lecture
Les apprenants configureront les préférences de lecture primary, primaryPreferred, secondary, nearest et avec balises afin de répartir les lectures sur le jeu de réplicas.
Préférences de lecture : répartir la charge de lecture est une leçon MongoDB Academy gratuite sur CoddyKit. Ceci est la leçon 4 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage MongoDB Academy, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours MongoDB Academy comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
What Is a Read Preference?
A read preference controls which replica set member the driver sends read operations to. By default, all reads go to the primary to ensure you always see the latest data. However, redirecting reads to secondaries can reduce load on the primary and bring reads geographically closer to users — at the cost of potentially reading slightly stale data.
primary: Always Read From Primary
primary (the default) routes every read to the primary. This guarantees strong consistency — you will always read your own writes and see the most up-to-date data. The downside is that the primary handles all read and write traffic. Use this mode whenever stale data would be unacceptable, such as in financial applications or user-facing dashboards.
// Explicit primary read preference (this is the default)
const col = db.collection('accounts', {
readPreference: 'primary'
})
await col.findOne({ _id: userId })primaryPreferred: Fallback to Secondary
primaryPreferred reads from the primary when it is available but falls back to a secondary if the primary is unreachable. This provides a balance: you normally get fresh data, but the application degrades gracefully during primary elections. Be aware that during the fallback, you may read data that is a few seconds behind.
const col = db.collection('products', {
readPreference: 'primaryPreferred'
})
await col.find({}).toArray()secondary: Read Only From Secondaries
secondary sends all reads to available secondaries, never touching the primary. This is ideal for analytics queries, batch jobs, or reporting that can tolerate eventual consistency. It offloads significant read pressure from the primary. If no secondary is available, the operation fails — it will NOT fall back to the primary.
// Route analytics query to secondary
const col = db.collection('events', {
readPreference: 'secondary'
})
const count = await col.countDocuments({ type: 'click' })secondaryPreferred: Secondary With Fallback
secondaryPreferred prefers secondaries but falls back to the primary if no secondary is available. This is the most commonly used non-default mode — it spreads read load across secondaries under normal conditions while remaining available when a secondary goes down. The caveat is the same as secondary: reads may be slightly stale.
const col = db.collection('catalog', {
readPreference: 'secondaryPreferred'
})
await col.find({ category: 'books' }).toArray()nearest: Lowest Network Latency
nearest sends reads to the member with the lowest measured network round-trip time, regardless of whether it is primary or secondary. This is perfect for globally distributed applications where users in different regions should read from the closest data center. Note that different users may read from different members, so they may temporarily see different data states.
const col = db.collection('content', {
readPreference: 'nearest'
})
await col.findOne({ slug: 'hello-world' })Tag Sets: Targeting Specific Members
Tag sets let you label replica set members (e.g., { region: 'us-east' }, { purpose: 'analytics' }) and then write read preferences that target only matching members. This enables sophisticated routing: send application reads to the nearest region and analytics queries to a dedicated secondary, all within the same replica set.
// Tag a member in replica set config
let cfg = rs.conf()
cfg.members[2].tags = { region: 'eu-west', purpose: 'analytics' }
rs.reconfig(cfg)
// Read from eu-west analytics member
const col = db.collection('reports', {
readPreference: new ReadPreference('secondary', [{ region: 'eu-west' }])
})Stale Reads and Replication Lag
When reading from secondaries, you may encounter stale reads — the secondary hasn't replicated the latest writes from the primary yet. The staleness depends on replication lag. MongoDB 3.6 introduced maxStalenessSeconds: the driver refuses to use a secondary lagging more than the specified number of seconds, preventing very stale reads.
// Reject secondaries more than 90 seconds behind
const col = db.collection('products', {
readPreference: new ReadPreference(
'secondaryPreferred',
[],
{ maxStalenessSeconds: 90 }
)
})Read Preference in the Connection String
You can set the default read preference for all operations in the connection string using the readPreference parameter. This is the easiest way to configure the default without changing every call site. Individual operations can still override it by passing a readPreference option explicitly.
// Connection string with secondaryPreferred default
const uri = 'mongodb+srv://host/db?readPreference=secondaryPreferred&maxStalenessSeconds=120'
const client = new MongoClient(uri)Read Preference and Transactions
Multi-document transactions must always use primary read preference. Operations inside a transaction that specify a different read preference will throw an error. This ensures that all reads within the same transaction see a consistent snapshot as of the transaction's start time on the primary.
// Inside a transaction, reads always go to primary
const session = client.startSession()
await session.withTransaction(async () => {
// This implicitly uses primary read preference
const order = await db.orders.findOne({ _id: orderId }, { session })
await db.inventory.updateOne({ sku: order.sku }, { $inc: { qty: -1 } }, { session })
})Choosing Read Preference in Practice
Use this guide: Real-time user data (cart, profile, notifications) → primary. Product catalog, content → secondaryPreferred. Reports and analytics → secondary with a dedicated analytics member. Global CDN-like reads → nearest. Always measure replication lag before routing critical reads to secondaries.
Quick Check
Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.
Lesson Recap
In this lesson you learned: read preferences control which replica set member handles read operations, secondary and secondaryPreferred offload read traffic at the cost of eventual consistency, and nearest minimises latency in geo-distributed deployments. Next up we explore sharding — MongoDB's strategy for scaling beyond a single replica set.
Questions Fréquemment Posées
La leçon « Préférences de lecture : répartir la charge de lecture » est-elle gratuite ?
Oui — le texte complet de « Préférences de lecture : répartir la charge de lecture » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours MongoDB Academy, passe à CoddyKit PRO. Le cours MongoDB Academy comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Préférences de lecture : répartir la charge de lecture » ?
Les apprenants configureront les préférences de lecture primary, primaryPreferred, secondary, nearest et avec balises afin de répartir les lectures sur le jeu de réplicas. Tu pratiques MongoDB Academy avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer MongoDB Academy ?
Aucune expérience préalable n'est requise. MongoDB Academy sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 4 sur 4.
Combien de temps prend la leçon « Préférences de lecture : répartir la charge de lecture » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon MongoDB Academy ?
Oui. Chaque leçon MongoDB Academy inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Membres d’un jeu de réplicas : primaire, secondaires et arbitre
- Élections et basculement automatique
- Préoccupations d’écriture et durabilité confirmée
- Préférences de lecture : répartir la charge de lecture