Object Store v2 FAQ
APAC: Tokyo (ap-northeast-1), Singapore (ap-southeast-1), and Sydney (ap-southeast-2). EU: Frankfurt (eu-central-1), Ireland (eu-west-1), and London (eu-west-2). North America: Central Canada (ca-central-1), Northern Virginia (us-east-1), and Oregon (us-west-2). South America: Sao Paulo (sa-east-1).
Yes. For example, if you deploy to the Singapore region, the object store persists in the Singapore region.
In OSv2 there is no limit on the number of keys per application. In Object Store v1, the limit was 100,000 keys and attempts to store more were rejected.
This API is available in the Anypoint Platform Developer’s portal. See link below.
You can use Anypoint Studio to download from Anypoint Exchange the Mule 3 Object Store connector or the Mule 4 Object Store connector. In Mule 4, OSv2 is a core connector that is pre-installed in Mule 4 and in Anypoint Studio 7. Note: The Mule 3 Object Store connector writes a key-value pair, whereas the Mule 4 Object Store connector writes a key-list pair. See links below.
The Mule 3 Object Store connector works for both OSv1 and OSv2. The Mule 4 Object Store connector only works with OSv2. See links below to each connector.
Free accounts are rate limited to 10 transactions per second per application. Premium customers who purchase the Object Store SKU have no rate limits; however, the number of API requests premium customers can make is limited by their subscription value. If a free account application exceeds the rate limit, the 429 HTTP status code results.
An Object Store and its contents (keys, values) is accessible to all CloudHub workers of the one Mule application that defines and therefore owns that Object Store. However, other Mule applications and the CloudHub workers on which they execute cannot access this Object Store and its contents. If needed, you can use the REST API to read from one application and store to another.
No, but applications running on-premises can use the OSv2 REST API to store data in OSv2 and retrieve it.
Object Store v2 uses TLS for secure transport. Data at rest is stored using FIPS 140-2 compliant encryption standards.
We recommend that you encrypt sensitive data before writing it to the Object Store.
Object Store V2 does I/O for each read and write. With Object Store V2, the API call is localized to the same data center as the Runtime Manager application.