Is it a good idea to use mongodb , inmemory db and postgres together? [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 8 years ago.

Our application deals with both report and transactions (OLAP and OLTP).

The application needs to display the generated report in form of charts and tables. And other part of application deals with data gathering and manipulation(CRUD operations).

As a part of our solution strategy:

1. Will keep the most accessed report data in the inmemory db giving an upper limit to inmmory db size?

2. Postgres for storing all datas required for the application

3. Mongodb for regularly collecting data required for reports from the postgres db.

Answer 1

No. The simplest design is the best design, unless your requirements dictate something more complex is needed. PostgreSQL alone is mature and proven, and can be tuned to cache data in memory as well. I recommend building directly on PostgreSQL until you find that performance is not sufficient. I use PostgreSQL as our sole database technology for a busy national website and it works great.

At least choose one database to start with instead of three.