New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CosmosDB connector #1663

Open
nicojdejong opened this Issue Jan 17, 2018 · 12 comments

Comments

Projects
None yet
@nicojdejong
Copy link

nicojdejong commented Jan 17, 2018

CosmosDB is Microsofts new cloud database

It would be great to have a connector for this database

@sorenbs

This comment has been minimized.

Copy link
Member

sorenbs commented Jan 17, 2018

Thanks @nicojdejong

Can you describe your particular use case? Are you already using Cosmos?

@nicojdejong

This comment has been minimized.

Copy link
Author

nicojdejong commented Jan 17, 2018

@tedwardc

This comment has been minimized.

Copy link

tedwardc commented Jan 31, 2018

Hi Soren,

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 :)

Best,
Ed

@benmccallum

This comment has been minimized.

Copy link

benmccallum commented Mar 9, 2018

+1

@mmeckes

This comment has been minimized.

Copy link

mmeckes commented Mar 22, 2018

+1 from me too. We are using Cosmos DB on a bunch of chat tools because it is easy to use from the Azure Bot Framework. Having a GraphQL connector would be really useful.

@infin8loop

This comment has been minimized.

Copy link

infin8loop commented Apr 12, 2018

+1 We are making a foray into Cosmos DB after starting out with graphcool. Lack of other database support is probably our biggest hurdle for Prisma (i.e. we want MS SQL, Cosmos DB or Postgres).

@sorenbs

This comment has been minimized.

Copy link
Member

sorenbs commented Apr 12, 2018

Thank you all!

We have finished the ground work required to support more database connectors. The implementation of Postgress is set to start next week and more will follow soon after. I can't offer a concrete timeline for Cosmos DB yet though.

@kevineger

This comment has been minimized.

Copy link

kevineger commented Nov 8, 2018

@sorenbs great news! Any update on a Cosmos DB roadmap? I'd potentially be interested in contributing.

@stale

This comment has been minimized.

Copy link

stale bot commented Jan 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

@AronT-TLV

This comment has been minimized.

Copy link

AronT-TLV commented Jan 10, 2019

Has anyone tested the MongoDb connecter with CosmosDB - it supports the Mongo wire do in principle it should work

@stilren

This comment has been minimized.

Copy link

stilren commented Jan 16, 2019

@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:secret==@dbname.documents.azure.com:10255/?ssl=true&replicaSet=globaldb"

@AronT-TLV

This comment has been minimized.

Copy link

AronT-TLV commented Jan 30, 2019

Thanks @stilren

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment