A Mule application deployed to multiple CloudHub 2.

Object Store v2 is suitable for distributed key/value state that must be available across CloudHub executions and replicas, but it should not be used to hold the complete contents of files larger than its per-value limit. MuleSoft documents that an Object Store v2 value is limited to 10 MB, while the overall store does not have a fixed aggregate size limit.

The appropriate architecture is therefore to persist the binary file itself in storage designed for large objects—for example, a durable external object/blob storage service—and store only lightweight metadata in Object Store v2. That metadata can include the object's storage key, URI/location, status, or other lookup information. Subsequent flow executions can query Object Store v2 to determine whether the object exists and then retrieve the actual file from the external storage system.

An in-memory Object Store is inappropriate because application replicas do not provide a durable shared in-memory persistence model for this requirement. Storing the entire file directly in Object Store violates the 10 MB value constraint. Local file-based storage is also unsuitable as a cross-replica CloudHub persistence mechanism.

Reference topics: Object Store v2 limits; CloudHub replicas; distributed persistence; external object storage; key/location metadata.

Official documentation: https://docs.mulesoft.com/object-store/osv2-faq

===============================================================