generated from hyper63/adapter-template
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support MongoDB Atlas Data Api and Native Driver #32
Labels
enhancement
New feature or request
Comments
TillaTheHun0
changed the title
Support MongoDB Atlas Data Api and Native
Support MongoDB Atlas Data Api and Native Driver
Jun 2, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 4, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 4, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 6, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 6, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Jun 7, 2023
TillaTheHun0
added a commit
that referenced
this issue
Aug 17, 2023
TillaTheHun0
added a commit
that referenced
this issue
Aug 17, 2023
TillaTheHun0
added a commit
that referenced
this issue
Aug 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are two main ways prescribed to consume MongoDB: the Atlas Data Api and the native driver
Ideally, this adapter supports both, and can be configured to either use the Atlas Data Api or the Native Driver. I envision this as a configuration parameters to be passed into the adapter. Or perhaps which consumption strategy can be inferred from the connection string protocol.
Ultimately, the internal abstraction should be such that the adapter methods don't need to know which consumption strategy they're using. The adapter methods should just consume a "mongo client" api.
The text was updated successfully, but these errors were encountered: