Data provider: what database to store data

[nicola]

I suppose MongoDB we can just throw stuff into and not care much about the structure of data. This would simplify #4 since there are existing rest library, discuss

[SnubbleJr]

I Think a simple SQLite would work, I can design the structure if you want.

[nicola]

Thing is that there is no reason to be bound to the data scheme especially if we want to move fast. Whoever is taking this, will possibly be in the data provider team, so it's good you all agree on this

[himerzi]

I'd suggest using a hosted solution. Particularly because later on this will have to integrate with the work the visualisation team is doing - and you guys don't want to be re-inventing the wheel when it comes to exposing your SQLite DB to the front end.

What about using something like Firebase, Parse, or MongoLab (this is probably the most "powerful" solution out of the three). Or indeed a hosted SQLite provider. All of these have Javascript SDK's that we could easily integrate with on the Vis team.

[xalodni]

Rethinkdb can do joins unlike Mongodb.

[nicola]

Getting experimental here @xalodni. I agree with @himerzi, the least we can do on this, the more we can focus on the core product.

[nicola]

Ok, @navidhg chosed MySQL