I work in a product which is tightly coupled to RDBMS - if we switch to NoSQL will tha add any value

[Nagarajan Lakshamanan]

Hi Team,

I work in a product which is tightly coupled to RDBMS and also we have concept of datawareshouse. (OLAP)
We use separate ETL jobs to load data ware house(OLAP) which is used for reporting purposes and where as our application will be using OLTP.


Can we use NoSQL as a single source of data for both OLAP and OLTP?

If we switch to NoSQL will it have an effect in performance?

Regards,
Naga

[Joe San]

Nagarajan Lakshamanan wrote:Hi Team,

I work in a product which is tightly coupled to RDBMS and also we have concept of datawareshouse. (OLAP)
We use separate ETL jobs to load data ware house(OLAP) which is used for reporting purposes and where as our application will be using OLTP.


Can we use NoSQL as a single source of data for both OLAP and OLTP?

If we switch to NoSQL will it have an effect in performance?

Regards,
Naga

NoSQL databases are designed to address the needs of ever expanding data and the potential bottlenecks that arise with the traditional RDBMS databases which fail to scale with such data volumes. Of course you will have a hit in performance if you use a NoSQL database like an RDBMS.

Most of the NoSQL databases like MongoDB, Cassandra, OpenTSDB to name a few are meant to be run on multiple hosts and by running them this way, you get scalability, reliability, high availability. It does not matter what you do with your data (OLAP or OLTP).

[Palak Mathur]

After having used NoSQL for sometime now, I would prefer Polyglot Persistence over one DB for all needs. Analyze and decide which db suits your needs.