Skip to content
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

Consider MongoDB variant #1

Open
mikeckennedy opened this issue Sep 5, 2017 · 2 comments
Open

Consider MongoDB variant #1

mikeckennedy opened this issue Sep 5, 2017 · 2 comments

Comments

@mikeckennedy
Copy link
Owner

Swap out SQLAlchemy for MongoDB (in a separate branch or separate repo altogether).

Who's interested in this?

@datatalking
Copy link

What advantages would MongoDB offer in this situation, from what I understand, I think Mongo decreases the cache or loading times by moving the needed files out of SQL and into a cache?

Am I close?

@mikeckennedy
Copy link
Owner Author

Hi,

There are lots of trade offs and considerations when thinking MongoDB (document db in general) vs. relational. But to me it comes down to two things.

  1. The MongoDB versions tend to be way faster. For example, https://training.talkpython.fm/ gets 10's of millisecond response times with zero caching and what would require lots of joins in RDBMS.
  2. Simplicity. I almost NEVER need to do a migration to keep my db up-to-date with my models. MongoDB just adjusts. If I used SQLAlchemy, I would be constantly juggling DB schemas as I release new versions with a tiny bit of "planned down time".

But my goal with this issue here is to simply make the template have an option (want MongoDB or SQLAlchemy?) so people can pick easily. :)

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

No branches or pull requests

2 participants