Comments on: Two Cons against NoSQL. Part I. http://www.odbms.org/blog/2012/10/two-cons-against-nosql-part-i/ Trends and Information on New Data Management Technologies, Innovation. Wed, 17 Apr 2013 21:47:18 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Dražen Lučanin http://www.odbms.org/blog/2012/10/two-cons-against-nosql-part-i/comment-page-1/#comment-7506 Dražen Lučanin Tue, 06 Nov 2012 12:13:01 +0000 http://www.odbms.org/blog/?p=1785#comment-7506 I think the biggest issue with porting data from a NoSQL DB such as MongoDB to a traditional SQL DB such as MySQL is that Mongo is schemaless - i.e. it allows you to create structures which don't fit into a traditional relational DB. Personally, I don't really see this as a drawback, because if you build your application relying on this "slackness" feature, you obviously did it intentionally by skipping some strict organisation in the beginning. You would have to do it later on before fitting this data in a more firmly structured DB. I think the biggest issue with porting data from a NoSQL DB such as MongoDB to a traditional SQL DB such as MySQL is that Mongo is schemaless – i.e. it allows you to create structures which don’t fit into a traditional relational DB.

Personally, I don’t really see this as a drawback, because if you build your application relying on this “slackness” feature, you obviously did it intentionally by skipping some strict organisation in the beginning. You would have to do it later on before fitting this data in a more firmly structured DB.

]]>