Please enable JavaScript.
Coggle requires JavaScript to display documents.
Storage Databases - Coggle Diagram
Storage Databases
NoSQL
Mongodb
With NoSQL you’re more likely to run into tough problems without documented solutions which can lead to delays
-
-
NoSQL frameworks provide tools to monitor, backup, and maintain NoSQL databases.
Both SQL and NoSQL offer high availability and auto-replication (automatically communicating with another instance when one goes down), but SQL requires configuration while many NoSQL databases automatically include these features.
When to Use
You are constantly adding new features, functions, data types, and it’s difficult to predict how the application will grow over time.
Changing a data model is SQL is clunky and requires code changes. A lot of time is invested designing the data model because changes will impact all or most of the layers in the application
In NoSQL, we are working with a highly flexible schema design or no predefined schema. The data modeling process is iterative and adaptive. Changing the structure or schema will not impact development cycles or create any downtime for the application.
-
You have a lot of data, many different data types, and your data needs will only grow over time.
NoSQL makes it easy to store all different types of data together and without having to invest time into defining what type of data you’re storing in advance.
Your data needs scale up, out, and down.
-
BASE
Basic availability , soft state (don't have to be write consistent) , eventual consistency.
SQL
MySQL
-
SQL is mature and supported by a strong technical community, your engineers won’t run into problems they can’t solve
-
When to Use
-
-
You need to ensure ACID compliance (Atomicity, Consistency, Isolation, Durability) or defining exactly how transactions interact with a database.
-
ACID
Automacity
A transaction is an atomic unit; hence, all the instructions within a transaction will successfully execute, or none of them will execute.
consistency
A database is initially in a consistent state, and it should remain consistent after every transaction.
Isolation
If the multiple transactions are running concurrently, they should not be affected by each other
Durability
Changes that have been committed to the database should remain even in the case of software and hardware failure.
-