Adobe I/O runtime uses Couch DB or Cosmos DB | Community
Skip to main content
E
eldhov19157560
Level 2
October 22, 2020
Solved

Adobe I/O runtime uses Couch DB or Cosmos DB

  • October 22, 2020
  • 2 replies
  • 1968 views

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/quickstart.md

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

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by duynguyen_adobe

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/quickstart.md.

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?

2 replies

D
Adobe Employee
duynguyen_adobeAdobe EmployeeAccepted solution
Adobe Employee
October 22, 2020

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/quickstart.md.

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?

E
eldhov19157560Author
Level 2
October 22, 2020
@duypnguyn, Nothing specific, I was referring the technical details (background) again for an internal technical discussion and accidently noticed the conflicting sentenses.Thats it. 🙂
M
Adobe Employee
mihai-corlanAdobe Employee
Adobe Employee
October 22, 2020

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

Terms & ConditionsAccessibility statement

Loading footer...