What is the relationship between OSv2 and CloudHub workers?

What is the relationship between OSv2 and CloudHub workers?

• A. OSv2 data is shared between all CloudHub workers when persistent.
• B. OSv2 stores data only locally per worker.
• C. OSv2 does not work with CloudHub.
• D. OSv2 is a database.

Answer: (A)

OSv2 on CloudHub provides a shared persistent data area that all workers of an app can access when persistence is enabled. The idea being tested is that the OSv2 data store isn’t confined to a single worker; once persistence is turned on, every CloudHub worker can read and write to the same data set, allowing state to be shared as the app scales horizontally. If persistence isn’t enabled, each worker gets its own isolated OSv2 store, so data isn’t shared across workers. OSv2 isn’t a database itself; it’s a runtime storage layer used by CloudHub, while you may still use a separate database for durable data. So the correct understanding is that OSv2 data is shared between all CloudHub workers when persistence is enabled.

OSv2 on CloudHub provides a shared persistent data area that all workers of an app can access when persistence is enabled. The idea being tested is that the OSv2 data store isn’t confined to a single worker; once persistence is turned on, every CloudHub worker can read and write to the same data set, allowing state to be shared as the app scales horizontally. If persistence isn’t enabled, each worker gets its own isolated OSv2 store, so data isn’t shared across workers. OSv2 isn’t a database itself; it’s a runtime storage layer used by CloudHub, while you may still use a separate database for durable data. So the correct understanding is that OSv2 data is shared between all CloudHub workers when persistence is enabled.