Object Store v2 and persistent stores by deployment
Where an object store actually keeps its data on CloudHub 1.0, CloudHub 2.0, Runtime Fabric and an on-premises cluster, and the Object Store v2 limits, billing, security and control-plane rules that decide whether it fits a design.
Design Mule applications using Object Stores (OSs), the OS Connector, and OS services in all deployment options.
~8 min read · 11 practice questions
What the exam expects
- Choose the store that keeps data across restarts and replicas on CloudHub 1.0, CloudHub 2.0, Runtime Fabric, standalone runtimes and on-premises clusters.
- Apply Object Store v2 limits (TTL, entries, keys, values, transactions) and its billing rules to a design.
- Recognize where Object Store v2 is available by control plane and what to deploy to instead.
- Plan Persistence Gateway on Runtime Fabric and explain how the Object Store Connector reaches it.
- Predict object store behavior under the Quorum Protocol, and decide when values need application-side encryption.
Object store: a facility Mule uses to persist data for later retrieval (Object stores). Object Store v2: the CloudHub service that stores data and states across batch processes, components and applications (Object Store v2 Overview). Persistence Gateway: Runtime Fabric's store shared across replicas and restarts (Persistence Gateway). TTL: time to live, after which an entry is evicted.
Key facts
- Detail
- 1 second to 2592000 s; out-of-range set to 30 days silently
- Detail
- Unlimited; Max entries not configurable for v2
- Detail
- 1024 bytes UTF-8; no pipe; spaces become plus
- Detail
- 10 base, 100 premium, per app; 429 when exceeded
- Detail
- Each 100 KB of payload per successful request
- Detail
- 100 million transactions per org, all environments
- Detail
- Encrypt in the app before writing
- Detail
- Not supported
- Detail
- Volatile disk, cleared on restart or redeploy
- Detail
- All object store access routes to v2
- Detail
- Object store operations fail in the minority partition
Sources for this section (6)
- Object Store v2 Overviewdocs.mulesoft.com (opens in a new tab)
- Connector Referencedocs.mulesoft.com (opens in a new tab)
- FAQ: Object Store v2docs.mulesoft.com (opens in a new tab)
- Rate limiting and billingdocs.mulesoft.com (opens in a new tab)
- Clusteringdocs.mulesoft.com (opens in a new tab)
- HA cluster overviewdocs.mulesoft.com (opens in a new tab)
- Why does enabling Object Store v2 for a Mule 4 CloudHub application change where its default persistent store writes?
- When Use Object Store v2 is disabled and later reenabled for a CloudHub application, what happens to the stored pairs?
- How many billable units does storing one 250 KB value count?
- Which minimum Mule Maven plugin version can enable persistent object stores for Runtime Fabric deployments?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both