Skip to main content

What is NoSQL Database?

The name NoSQL itself tells us that it is a "non-SQL" or "non-relational" database. Around 30 years back when the data used to be non-changing and smaller in size, traditional relational databases were more prominent like ORACLE, Postgres and so on which had fixed schemas. But during the last decade, the data has grown exponentially and it is also changing quickly. The traditional databases have failed to handle this BIG DATA effectively. So there was a need to introduce a database that can adapt itself to ever-changing data and that can handle the enormous size of data. And thus NoSQL databases came into the picture.


Nowadays NoSQL databases have been referred to as "Not Only SQL" databases which mean that these databases may support SQL-like query languages and can be a part of polyglot persistent architecture along with other relational databases. The data structures used in the NoSQL database are more efficient than the data structures used by the relational database which makes the operations faster in the NoSQL database. Below are some of the features of NoSQL databases:

1. Flexibility: NoSQL databases offer flexible schema which makes NoSQL databases suitable for structured and unstructured data.

2. Scalability: NoSQL databases are scalable. It scale-out by using distributed clusters of hardware rather than scaling by adding expensive servers.

3. High Functionality: NoSQL provides high functional APIs and data types

4. High Performance: NoSQL databases are designed for specific data models and access patterns that enable high performance

Most of the NoSQL databases offer "eventual consistency" in which database changes are propagated to all the nodes eventually, so queries for data might not get the updated data immediately or might lead to inaccurate data, a problem called stale reads. Some NoSQL database also exhibits data loss. The other disadvantages include transaction management problems, Backup issues, and large document sizes in some of the NoSQL databases like MongoDB.

Types of NoSQL databases:


1. Key-Value: Key-Value stores use an associative array as a data model, the data is represented as key-value pairs where each key appears at most once in the collection. Some of the examples of Key-value stores are Memcached and Redis.

2. Document Store: In the document store, the data is represented as an object or JSON-like document because it is an efficient and intuitive data model. MongoDB is one such example of the document store

3. Graph: This kind of database is suitable for the data which exhibits a relationship between them and can be represented in the form of a graph consisting of elements with finite relationships between them. Popular databases include Neo4j and Giraph.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Backfill the Data in Airflow

In Apache Airflow, backfilling is the process of running a DAG or a subset of its tasks for a specific date range in the past. This can be useful if you need to fill in missing data, or if you want to re-run a DAG for a specific period of time to test or debug it. Here are the steps to backfill a DAG in Airflow: Navigate to the Airflow web UI and select the DAG that you want to backfill. In the DAG detail view, click on the "Graph View" tab. Click on the "Backfill" button in the top right corner of the page. In the "Backfill Job" form that appears, specify the date range that you want to backfill. You can use the "From" and "To" fields to set the start and end dates, or you can use the "Last X" field to backfill a certain number of days. Optional: If you want to backfill only a subset of the tasks in the DAG, you can use the "Task Instances" field to specify a comma-separated list of task IDs. Click on the "Star...
Post a Comment
Read more

How to use Cloud Function and Cloud Pub Sub to process data in real-time

Cloud Functions is a fully-managed, serverless platform provided by Google Cloud that allows you to execute code in response to events. Cloud Pub/Sub is a messaging service that allows you to send and receive messages between services. You can use Cloud Functions and Cloud Pub/Sub together to build event-driven architectures that can process data in real-time. Here is a high-level overview of how to use Cloud Functions with Cloud Pub/Sub: Create a Cloud Pub/Sub topic: The first step is to create a Cloud Pub/Sub topic that you will use to send and receive messages. You can do this using the Cloud Console, the Cloud Pub/Sub API, or the gcloud command-line tool. Create a Cloud Function: Next, you will need to create a Cloud Function that will be triggered by the Cloud Pub/Sub topic. You can create a Cloud Function using the Cloud Console, the Cloud Functions API, or the gcloud command-line tool. When you create a Cloud Function, you will need to specify the trigger type (in this case, C...
Post a Comment
Read more

How to migrate data from on-premise Postgres to Google Cloud

There are several ways to move data from an on-premise PostgreSQL database to Google Cloud. Here are three common approaches: Use a Cloud Data Integration Tool: Google Cloud offers several tools that can help you move data from an on-premise PostgreSQL database to the cloud. For example, Cloud Data Fusion is a fully-managed, cloud-native data integration platform that can help you build, execute, and monitor data pipelines between various data sources and destinations, including PostgreSQL and Google Cloud. You can use Cloud Data Fusion to extract data from your on-premise PostgreSQL database, transform the data as needed, and load the data into a cloud-based data store, such as BigQuery or Cloud SQL. Use a Command-Line Tool: Another option is to use a command-line tool, such as pg_dump or pg_dumpall, to extract the data from your on-premise PostgreSQL database and save it to a file. You can then use a tool such as gsutil to upload the file to Google Cloud Storage. Once the data is i...
Post a Comment
Read more