A production service of Universal Resolver

[Muhammad-Altabba]

What is the recommended way to have/connect to a production service?
Do you recommend that every project that needs the DID Universal Resolver to run this repository with all its docker containers on the company premises or on its own cloud servers? Or is there another preferred way?
Thanks,

[BernhardFuchs]

For production you can run the application in this repo with a chosen subset of drivers on your own infrastructure.
Just remove the drivers you don't want to use from the config.json and docker-compose file in the root directory.
If you run the Universal Resolver on-premise or on cloud servers is up to you, also if you chose docker-compose, kubernetes or some other container orchestration tool.

https://dev.uniresolver.io is run on an AWS/EKS kubernetes cluster and https://resolver.identity.foundation is run on IBM kubernetes infrastracture. The ci folder holds the logic for the AWS deployment which you can use to get started, if kubernetes is your choice. There is also a community effort to create a helm chart for the application but I'm not aware of the current state of this project.

We at Danubetech are working on a SaaS system for managing DID's which includes the Universal Resolver. This product is currently in Alpha state and will go live for public use by approx mid 2021.

[BernhardFuchs]

@Muhammad-Altabba Are there still open questions to that issue? Otherwise I will close it.

[peacekeeper]

We have an open PR with some ideas on hosting instances of the Universal Resolver: #214