News for hackers. Stuff that matters.
Re:Aggregating NBA data, PostgreSQL vs MongoDB by raphinou on Tuesday February 18, 2014 @08:04AM (#7257882)
I've migrated data I stored in mongo to a postgresql, but kept it in json format. The ease of querying this brought is impressive thanks to postgresql's json support. The only problem I encountered was with nested json objects. I keep telling myself I should blog about it, to illustrate data collection framework for smaller shops for who it wouls be overkill to deploy Hadoop or Cassandra.
Re:Aggregating NBA data, PostgreSQL vs MongoDB by MetaCosm on Wednesday February 19, 2014 @12:51AM (#7262052)
Our team recently did something similar. We went from MongoDB to PostgreSQL. We converted most of our well known fields over to proper PostgreSQL fields, and by using UUIDs in PostgreSQL we still had opaque sharable ids. On top of that, for developer flexibility, we included a little json dumping ground column in most of our tables. This allows developers to quickly add in some data they care about without dealing with migrations and database versioning. Then, as needed (and only if needed) we move the data out of json to proper columns, mostly for performance or relational reasons.