Azure Cosmo Db vs Mongo db Native

[AngelOCrzAkky94]

Hello, how are you?
Hi, how are you? I'm Angel Ortiz from the TEC.credentials team at Tecnológico de Monterrey.

I have some questions:
This week I tried to create the container with the image digitalcredentials/status-service-db:0.1.0 but I get an error or errors with cosmo db. I would like to know if the connector you are currently using to do the migrations to create the tables is compatible with this technology.

Well, currently I have my connection string configured this way. If cosmo db is not an option I would like you to comment on it shortly since we have not had problems with the payload.

Connection string
mongodb://usersmo:passcosmo@servercosmo:10255/statusdb?ssl=true&tls=true&tlsAllowInvalidCertificates=true&retrywrites=false&replicaSet=globaldb&serverSelectionTimeoutMS=30000&maxIdleTimeMS=120000&authSource=statusdb&directConnection=true

Attached evidence 1:

Attached evidence 2:

Thanks...

[alexfigtree]

@AngelOCrzAkky94 We're currently using mongoDb and are not familiar with Cosmo, but we'd recommend troubleshooting the cosmo-specific errors on your end. If you find answers to your questions, we encourage you to share them with us, as there may be others facing similar issues.

[AngelOCrzAkky94]

I found this article about an issue that raises what I just told you.

prisma/prisma#11921

I have a question about this variable STATUS_CRED_SITE_ORIGIN. Is it creating a web api that returns the status credential? For security reasons, they do not allow us to generate the pipe or localtunnel. We do not have public output since our Azure containers are on a private network.
In our case if we could generate a masked api web service that returns the status credential of this StatusCredential table?

These were the tables that were created

[AngelOCrzAkky94]

...........