this post was submitted on 02 Mar 2025
38 points (97.5% liked)

Learn Programming

1625 readers
66 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
38
What is NoSQL good for? (programming.dev)
submitted 1 day ago by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

I’m versed enough in SQL and RDBMS that I can put things in the third normal form with relative ease. But the meta seems to be NoSQL. Backends often don’t even provide a SQL interface.

So, as far as I know, NoSQL is essentially a collection of files, usually JSON, paired with some querying capacity.

  1. What problem is it trying to solve?
  2. What advantages over traditional RDBMS?
  3. Where are its weaknesses?
  4. Can I make queries with complex WHERE clauses?
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 1 day ago* (last edited 1 day ago)

Pretty much. The advantage is not really the unstructeredness per se, but simply the speed at which you can get a single record and the throughput in how much you can write. It's essentially sacrificing some of the guarantees of ACID in return for parallelization/speed.

Like when you have a million devices who each send you their GPS position once a second. Possible with RDBS but the larger your table gets, the harder it'll be to get good insertion/retrieval speeds, you'd need to do a lot of tuning and would essentially end up at something like a NoSQL database effectively.