15 Matching Annotations
  1. Apr 2023
    1. a ausência de um esquema de dados bem definidopara os dados necessários de um cliente possa sercorretamente modelada e implementada em um ge-renciador de banco de dados adequado

      A alternativa (A) está correta. A adoção de um banco de dados NoSQL é uma solução viável quando se tem dados não estruturados ou semi-estruturados, pois esses bancos de dados não possuem um esquema de dados rígido, permitindo uma modelagem mais flexível dos dados. Isso significa que a ausência de um esquema de dados bem definido para os novos dados dos clientes pode ser facilmente modelada e implementada em um gerenciador de banco de dados NoSQL.

      Por outro lado, um banco de dados relacional exige uma estrutura rígida e bem definida dos dados, o que dificulta o armazenamento de dados não estruturados ou semi-estruturados.

  2. Feb 2023
    1. Most applications do not need to process massive amounts of data. This has led to a resurgence in data management systems with traditional architectures; SQLite, Postgres, MySQL are all growing strongly, while “NoSQL” and even “NewSQL” systems are stagnating.

      SQL still shines over NoSQL

  3. Dec 2022
  4. Aug 2022
  5. Feb 2022
    1. NoSQL 数据库的问题在于,随着时间的流逝,你的简单模型不可避免地变得越来越复杂,然后它不再起作用。在过去的十年中,我已经意识到使用 RDBMS 数据库基本上是100%的正确选择

      Hacker News 读者

      当没想清楚的时候尽量选择 RDBMS, 之后根据去调整.

  6. Jul 2020
    1. So in brief, for our application service, if we understand the access patterns very well, they’re repeatable, they’re consistent, and scalability is a big factor, then NoSQL is a perfect choice.

      When NoSQL is a perfect choice

    2. Comparison Time … 🤞

      Brief comparison of 8 aspects between SQL vs NoSQL

  7. Jun 2020
    1. Cloud Firestore's NoSQL data model, you store data in documents that contain fields mapping to values
    1. NoSQL databases typically perform better and are easier to scale due to the nature of their data access and storage
  8. May 2020
    1. Which database technology to choose

      Which database to choose (advice from an Amazon employee):

      • SQL - ad hoc queries and/or support of ACID and transactions
      • NoSQL - otherwise. NoSQL is getting better with transactions and PostgreSQL is getting better with availability, scalability, durability
  9. Apr 2020
    1. If we refer to the CAP theorem, Mnesia sits on the CP side, rather than the AP side, meaning that it won't do eventual consistency, will react rather badly to netsplits in some cases, but will give you strong consistency guarantees if you expect the network to be reliable (and you sometimes shouldn't).

      We start out with the TL;DR treatise: The mnesia database is not CP, nor AP. And it cannot be CA, because CA doesn’t make any meaningful sense. In short, it is broken with respect to the CAP theorem. https://medium.com/@jlouis666/mnesia-and-cap-d2673a92850

  10. Apr 2018
    1. The takeaway from the article: Choose document-oriented database only when the data can be treated as a self-contained document