Database side: What to use? about dcaf_case_management HOT 6 CLOSED

If the primary needs for starting out are:

• non relational tables
• schema flexibility
• rapid development

MongoDB fits the use case for this project.

For encryption needs Symmetric Encryption is suitable option that works for any ruby ORM.

from dcaf_case_management.

@Kevin-Wei I'm into the symmetric encryption idea, and into the idea of using Mongo! I haven't used nosql before but have always meant to -- I'll do some reading up on it this coming week. Thank you very much for the suggestion!

I'm a little curious about the security aspect, since it's like the first question the DCAF board will ask about -- want to make sure that keeping patient data safe and private is as baked into the process here as flexibility and rapid development. Are you recommending we roll with Mongo at first and then swap to something else once we're past prototyping, or going with mongo the full way thru?

from dcaf_case_management.

I did some googling and it looks like heroku, among others, offer Mongo options. Two specifics:

https://elements.heroku.com/addons/mongolab
https://elements.heroku.com/addons/mongohq

pretty neat!

from dcaf_case_management.

I believe the conversation was to roll with Mongo at first and then swap to something once we're past prototyping.

from dcaf_case_management.

Mongo might not be a bad permanent solution. They just released 3.2 today and basically added joins with their implementation of $lookup aggregation. aka SQL Joins.

of course the downside is keeping track of private keys and the DB's themselves will need to be done manually

from dcaf_case_management.

To update this: We're going to roll with mongo for development for the time being. The initial stab is in pr #28 .

from dcaf_case_management.