Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
CosmosDB connector #1663
Dear Soren, No I am considering the techstack for a startup. A graph database will centrainly be part of it. Database as a service makes sense – as well as the fact that we are Microsoft focusses and will have some credits to burn on buying CosmosDB. I have a better feeling with GraphQL syntax and resources than going through one of the excisting connectors to CosmosDB. I discardd the idea of using GraphQL until I saw your connector. ArangoDB though was in view. It seems a great solution. So no. No implementation to be done at this time. I am sure though that either the community or Microsoft will bridge the gap…. Rgds, Nico
I second the request for supporting Cosmos Db. I too am working on a startup and would love to be able to use Cosmos Db as the data store for a GraphQL API. I chose Cosmos Db because I work with really large data sets (one is >250 GB) and they offer auto-indexing and fast response times.
I was beginning to think I needed to write a connector myself but I would much rather work on value-added features and not so much on plumbing if I could.
I've been running with Apollo-* stack and haven't seriously considered Graphcool because of this limitation but I would love to just leverage all the magic you guys have created and not worry about it :)
@AronT-TLV I gave it a quick shot trying to connect it to my cosmos db with mongodb api using the prisma init hello-world wizard with the error "no primary found in replicaset or invalid replica set name" -
The connection string looks like this: "mongodb://dbname:firstname.lastname@example.org:10255/?ssl=true&replicaSet=globaldb"