Home/ Questions/Q 6652437
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T01:08:18+00:00

I’ve got an upcoming project and I can’t decide whether to stick with SQL

  • 0

I’ve got an upcoming project and I can’t decide whether to stick with SQL or switch over to NoSQL. It’s basically a reporting system with the main interface being reporting on the data entered in by users.

Here’s the schema I’ve got mapped out:

enter image description here

Because this schema is so nested, I started thinking about NoSQL. With SQL, I’m afraid I’m going to have a crap-ton of joins to get to the bottom of the tree (the Record model).

My concerns, though, are two-fold:

  1. I’m only just starting to get into NoSQL and I’m worried my
    knowledge may limit me because of the tight timeframe.
  2. Although creating data at the bottom of the tree will probably be relatively simple, I’m worried that it may be hard to report on without getting into some heavy map/reduce stuff (that I have zero experience with)

My question:
Given my concerns, do you think this schema — because of how deeply nested it is — lends itself more to NoSQL? If so, do you think the reporting on the “records” will be difficult?

I realize that it may be difficult to answer these questions without more info, so please let me know what other info may be helpful in coming up with an answer.

Thanks in advance for your help!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Just my opinion:

    I Stared at diagram for approx 3 sec, this is clearly relational. Benefits of an RDBMS heavily outweigh a NoSQL solution here. Why would you want to use NoSQL? Are there 100,000+ records (may a million plus)? You need microsecond/millisecond performance?

    NoSQL, as I understand, is not because you don’t like lots of joins. It’s because big systems for hierarchical data don’t suit every situation. This suit this perfectly, however.

    • 0