Object Store v2 FAQ
OSv2 is available in every region where Runtime Manager applications can be deployed including:
APAC: Tokyo (ap-northeast-1), Singapore (ap-southeast-1), and Sydney (ap-southeast-2).
EU: Frankfurt (eu-central-1) and Ireland (eu-west-1).
North America: Central Canada (ca-central-1), Northern Virginia (us-east-1), and Oregon (us-west-2).
South America: Sao Paulo (sa-east-1).
Also London (eu-west-2) can be accessed from the US cloud, but not the EU cloud.
Yes. For example, if you deploy to the Singapore region, the object store persists in the Singapore region.
Object Store v2 data persists 30 days. OSV2 does not honor any TTL (Entry Ttl) setting set in the ObjectStore Connector. There is no flexibility in setting TTL (Entry Ttl). The expiry time is 30 days. The expiry time is reset if an update to that key occurs. If there is no update, the key is deleted at the 30 day mark.
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.
Anypoint Exchange provides assets for the Mule 3 Object Store connector used by Anypoint Studio 6 and the Mule 4 Object Store connector used by Studio 7.
The Mule 3 Object Store connector works for both OSv1 and OSv2. The Mule 4 Object Store connector only works with OSv2.
Customers who have not purchased a separate Object Store SKU are rate limited to 10 transactions per second per application. If a free account application exceeds the rate limit, further requests will not be processed for a time and a 429 HTTP error status code results. To go beyond the base 10 TPS rate limit, contact your MuleSoft account team.
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. If you require a higher level of security, 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.