cookiecutter-pyramid-talk-python-starter icon indicating copy to clipboard operation
cookiecutter-pyramid-talk-python-starter copied to clipboard

Published 20 hours ago • verified publisher icon mikeckennedy

Consider MongoDB variant

Open mikeckennedy opened this issue 8 years ago • 2 comments

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

Who's interested in this?

mikeckennedy avatar Sep 05 '17 04:09 mikeckennedy

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?

datatalking avatar Jul 01 '18 14:07 datatalking

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

mikeckennedy avatar Jul 02 '18 15:07 mikeckennedy