0

I'm creating a web application which will communicate with REST API which returns data in JSON. That data can be converted into relational data, of course, when I fetch it to store into a db which happens to be PostgreSql. But I'm thinking about using MongoDb instead because working with JSON is more natural for MongoDb.

Your thoughts, should I use MongoDb instead for that reason?

Incerteza
  • 32,326
  • 47
  • 154
  • 261
  • 1
    http://tapoueh.org/blog/2014/02/17-aggregating-nba-data-PostgreSQL-vs-MongoDB –  Jan 15 '15 at 14:45

2 Answers2

1

What the best option may be for you can depend on several factors:

  • How often are you going to poll the API?
  • How frequent are you going to be inserting into the DB?
  • How often are you going to read from the DB?
  • How fast will the data grow?
  • What is the structure of the actual data?

MongoDB horizontal scales very well meaning that if you are going to be polling the API frequently and inserting large volumes of data into your DB then it is relative easy to implement sharding and fire up another Mongo instance on another server. Difference between scaling horizontally and vertically for databases

Inserting JSON data into MongoDB would probably be simpler than converting it to a relational format and maybe doing several inserts where (assuming the JSON is formatted properly) you could just do a single insert. Or use mongoimport to import many JSON documents at once. If the API data changes quite often for instance new columns, then in a relational database you will have to create the columns using ALTER TABLE, whilst in MongoDB it will just store the JSON document.

If you want to know more info about MongoDB they do offer free online courses. The courses are 7 weeks long , Each week they release new video lectures and a new assignments which take a couple of hours to get through. https://university.mongodb.com/courses/catalog

Community
  • 1
  • 1
mrjamesmyers
  • 454
  • 4
  • 13
  • 1
    You can store a JSON document in Postgres the same way you would in MongoDB. –  Jan 15 '15 at 21:54
  • Okay in that case if your current implementation is Postgres it may be worth trying it out first rather than using another technology. If it serves your purpose then fantastic and if you reach a stumbling block it should be simple to move the same JSON data from Postgres to MongoDB in the future. – mrjamesmyers Jan 15 '15 at 22:43
0

There is one use case worth checking if you have any aggregation of data fields inside json structure . That is a use case which might need stickiness to RDBMS or in an advanced state maybe an OLAP store.

Vivek Gyaneshwar
  • 21
  • 1
  • 3
  • This would be better served as a comment than an answer. It doesn't answer the question – Dbz Jul 08 '16 at 17:24