HostGator Web Hosting
HostGator Web Hosting

[ad_1]

Basically I am trying to decide on if our data is a good use case to store in a nosql DB . Currently our data is stored in MS SQL , where we get a row per session.

​

In our data, we have sessions, users (IE customers) and flights.

​

Our data is currently stored by session. So each new session gets a new row. Each user might have multiple sessions on the same flight, or the same sesssion could also have the same user with multiple flights, or the same session can have multiple users.

​

The reason we started to think of using a could noSQL DB is to be able to get an aggregated look of the data in easier ways. IE the data is currently stored by session, but what if we want stats by user, or by flight, etc. The thought was a NoSQL DB makes it easier to query shopping data on different levels, be it on the user, session or flight level

​

The more I read about it, the more I think we should stick with SQL but just wanted opinions

[ad_2]

View Reddit by XamiusView Source

Categories: SQL

5 Comments

always_on_top123 · September 18, 2020 at 9:31 pm

noSQL allows for high-performance, agile processing of information at massive scale. It stores unstructured **data** across multiple processing nodes, as well as across multiple servers. As such, the **NoSQL** distributed database infrastructure has been the solution of choice for some of the largest **data** warehouse.

I would say it really depends on how much data there is, as well as what type of data there is. Based on my assumptions it seems like just a SQL DB should be fine, but depending on your needs (performance, data storage, data size) you may want to go the noSQL route, just my 2 cents.

sHORTYWZ · September 18, 2020 at 11:28 pm

I’m not really understanding why a properly structured SQL DB would not provide the views you’re using as examples.

What you’ve currently described is some very simple variations in SQL queries.

kagato87 · September 18, 2020 at 11:48 pm

How is your data structured currently? Is it a single table? It kinda sounds like you’re storing unstructured data in a sql database.

It sounds more like you need to get your data normalized. One user one row. One flight one row. One booked seat one row. Three tables. (To over simplify it a bit.)

The structure of sql is it’s real power, and unless you’re working at massive scales nosql might actually be a step backwards.

ATastefulCrossJoin · September 19, 2020 at 12:16 am

Shopping data is kind of the quintessential structured data. It is inherently relational (I.e products,customers, consumers).

Ask yourself this: do I need to update my data frequently? Do these updates need to be real time and consistent constantly? If the answer to these questions is yes I don’t think NoSQL is what you’re looking for.

Your post describes a need for perform any aggregation. While NoSQL can deliver this so can traditional RBMS. As you say you’re moving into the cloud, I would encourage you to look into data warehousing and the ease of auto scaling/partitioning your data which can get you excellent reporting performance while preserving vital ACID properties of the type of data you’re managing

Edit:
Just to be clear, I’m not a NoSQL hater by any means. I have seen magic worked with elastic search. But I do think transactional sales data is much more naturally suited to relational models in most scenarios

spacemonkeykakarot · September 19, 2020 at 12:19 am

Sounds like a SSAS dimensional model should handle the job?

Leave a Reply