top of page

Data Strategy

FAQ

Chess Game

If you are still trying to understand how Data Strategy can work for you, take a look at some frequently asked questions, along with helpful answers from the Ferrier team:

How many databases are currently on the market?

There are more than 340 databases currently on the market to pick from covering more than 12 different categories. These categories are, also, referred to as families. 

What is a SQL/Relational database?

A SQL database, also known as a Relational database, stores data in tables. In math terms, such tables are called relations. SQL is used to interact with the data.

Are SQL databases still a great option for many scenarios?

Yes, SQL databases provide great flexibility allowing your data points to be tied together in many ways. You don’t need to know exactly how you’re going to use your data ahead of time. 

Who are major players in the SQL database space?

Major players include PostgreSQL, Microsoft SQL Server, MySQL, and Oracle.

What is a NoSQL database?

A NoSQL database is a database that doesn’t fit in the SQL/Relational database category.

What are some of the top NoSQL Categories and their Major Players?

Top NoSQL categories include the following with many players crossing categories:

  • Document – MongoDB, Couchbase, Firebase, and Amazon DynamoDB

  • Key-Value – Redis and Amazon DynamoDB

  • Columnar / Wide Column – Cassandra, HBase, and Microsoft Azure Cosmos DB

  • Graph – Neo4j, OrientDB, and Microsoft Azure Cosmos DB

  • Time Series - InfluxDB, Kdb+, and Prometheus

When should I pick a NoSQL database?

NoSQL databases typically have a few scenarios they are great at and for which they are also designed. They can cause serious headaches when trying to force them to work for other scenarios. Each of the 12+ NoSQL categories has its own sets of benefits.

Do all Databases provide the critical features for my project?

Many projects require features covered by ACID-compliant databases. All of the major SQL/Relational databases adhere to ACID principles. This is not the case for some NoSQL databases. When considering a NoSQL database, be sure to consider which of the following ACID features are critical.

  • Atomicity - Transaction must execute completely or not at all. For example, if a bank account transfer is being made, both the withdrawal from one account and the deposit into the other account must be successful or the overall transaction fails.

  • Consistency - Data written to the database must conform to appropriate data validation rules.

  • Isolation - Guarantees each transaction's individuality.

  • Durability - Once a transaction has completed execution, the updates to the database are persisted in a way that is recoverable upon system failure.

Would you like professional guidance on which database to select or which reporting tool to select?

Our experience lets us pick the right options for your business needs. 

bottom of page