Expand my Community achievements bar.

SOLVED

Adobe I/O runtime uses Couch DB or Cosmos DB

Avatar

Level 3

While checking the runtime docs, I can see that the I/O runtime uses DB for storing and retrial of user details and action code.

In some pages the doc says Couch DB and other pages it says Cosmos DB. Could you please clarify this?

https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/qui...

https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/ove...

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @eldhov19157560 - I/O Runtime uses Cosmos DB to store user, action and activation records. Action code could be stored in Cosmos DB or a blob storage depending on its size. The information from your first link is accurate: https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/qui....

It's worth mentioning that, as I/O Runtime is Saas based, the internal components may change anytime without affecting the users' code and deployment.

Thanks for pointing out the inconsistency in the second link. We will work on the fix soon.

Could you please share why you are interested in this topic? Any restrictions on your side that one DB is preferred / not preferred than the other?

View solution in original post

3 Replies

Avatar

Correct answer by
Employee

Hi @eldhov19157560 - I/O Runtime uses Cosmos DB to store user, action and activation records. Action code could be stored in Cosmos DB or a blob storage depending on its size. The information from your first link is accurate: https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/qui....

It's worth mentioning that, as I/O Runtime is Saas based, the internal components may change anytime without affecting the users' code and deployment.

Thanks for pointing out the inconsistency in the second link. We will work on the fix soon.

Could you please share why you are interested in this topic? Any restrictions on your side that one DB is preferred / not preferred than the other?

Avatar

Level 3
@duypnguyn, Nothing specific, I was referring the technical details (background) again for an internal technical discussion and accidently noticed the conflicting sentenses.Thats it.

Avatar

Employee

Thank you for your attention to detail! I've just updated the docs to reflect that CosmosDB is the underlying database (we started with CouchDB so that's the reason we had this mix).

 

Cheers,

Mihai