-
Notifications
You must be signed in to change notification settings - Fork 3
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
Explore migrating from pymongo to motor as an async python libary for mongodb #787
Comments
i.e. https://github.com/mongodb-developer/farm-stack-to-do-app |
Hello, @mkshah605 — welcome to the project! @mkshah605 and @dwinston — While working on migrating nmdc-runtime/nmdc_runtime/api/db/mongo.py Line 15 in d7da63f
So, today, I was surprised when I noticed this ticket in the repo. |
Oops... correction: it is using both (and I think it's using nmdc-runtime/nmdc_runtime/api/db/mongo.py Lines 14 to 15 in d7da63f
nmdc-runtime/nmdc_runtime/api/db/mongo.py Lines 27 to 28 in d7da63f
Maybe someone was experimenting with |
@eecavanna yes, @elais was leading the experimentation with |
Given that there is now "official" guidance from MongoDB Inc. on using their official async python library for mongodb, i.e. motor, with FastAPI, explore pros/cons of migrating from using the older, more-stable-but-not-async pymongo library in order to take full performance advantage of FastAPI's async support.
The implication of this would be that a single-container deployment of the runtime would:
Goal: take some time to compare both approaches to better inform a path forward
The text was updated successfully, but these errors were encountered: