Kamran Ahmed
2 years ago
parent
1dac6caa56
commit
50a1f04c23
22 changed files with 153 additions and 21 deletions
@ -1 +1,10 @@ |
|||||||
# Sql vs nosql databases |
# SQL vs NoSQL databases |
||||||
|
|
||||||
|
SQL stands for Structured Query Language. It's used for relational databases. A SQL database is a collection of tables that stores a specific set of structured data. Some examples are PostgreSQL, MySQL, MariaDB etc. |
||||||
|
|
||||||
|
NoSQL stands for Not Only SQL. It's used for non-relational databases. A NoSQL database is a collection of collections that stores a specific set of unstructured data. Some examples are MongoDB, CouchDB, Redis etc. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=Q5aTUc7c4jg'>SQL vs. NoSQL: What's the difference?</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=cODCpXtPHbQ&t=22s'>Database Design Tips | Choosing the Best Database in a System Design Interview</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=FzlpwoeSrE0'>NoSQL vs SQL – Which Type of Database Should You Use?</BadgeLink> |
||||||
|
|||||||
@ -1 +1,9 @@ |
|||||||
# Normalization denormalization |
# Normalization vs Denormalization |
||||||
|
|
||||||
|
Database normalization is a process used to organize a database into tables and columns. The idea is that a table should be about a specific topic and that only those columns which support that topic are included. This limits the number of duplicate data contained within your database. This makes the database more flexible by eliminating issues stemming from database modifications. |
||||||
|
|
||||||
|
Denormalization is the opposite of normalization. It is the process of adding redundant data to a database to improve read performance. This is done by adding duplicate data into multiple tables to avoid expensive joins. This is done at the expense of increased storage and decreased write performance. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=sDU94hraq8g'>Normalization vs. Denormalization | Events and Event Streaming</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=UrYLYV7WSHM'>Normalization - 1NF, 2NF, 3NF and 4NF</BadgeLink> |
||||||
|
|||||||
@ -1 +1,7 @@ |
|||||||
# Entity relationship model |
# Entity Relationship Model |
||||||
|
|
||||||
|
Entity relationship model is a high-level data model that describes the logical structure of a database. It is a graphical representation of entities and their relationships to each other, typically used in modeling the organization of data within databases or information systems. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=QpdhBUYk7Kk'>Entity Relationship Diagram (ERD) Tutorial - Part 1</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=-CuY5ADwn24'>Entity Relationship Diagram (ERD) Tutorial - Part 2</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Ddl |
# DDL (Data Definition Language) |
||||||
|
|
||||||
|
DDL or Data Definition Language actually consists of the SQL commands that can be used to define the database schema. It simply deals with descriptions of the database schema and is used to create and modify the structure of database objects in the database. DDL is a set of SQL commands used to create, modify, and delete database structures but not data. These commands are normally not used by a general user, who should be accessing the database via an application. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/'>SQL | DDL, DQL, DML, DCL and TCL Commands</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Dml |
# DML (Data Manipulation Language) |
||||||
|
|
||||||
|
The SQL commands that deals with the manipulation of data present in the database belong to DML or Data Manipulation Language and this includes most of the SQL statements. It is the component of the SQL statement that controls access to data and to the database. Basically, DCL statements are grouped with DML statements. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/'>SQL | DDL, DQL, DML, DCL and TCL Commands</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Dql |
# DQL (Data Query Language) |
||||||
|
|
||||||
|
DQL statements are used for performing queries on the data within schema objects. The purpose of the DQL Command is to get some schema relation based on the query passed to it. We can define DQL as follows it is a component of SQL statement that allows getting data from the database and imposing order upon it. It includes the SELECT statement. This command allows getting the data out of the database to perform operations with it. When a SELECT is fired against a table or tables the result is compiled into a further temporary table, which is displayed or perhaps received by the program i.e. a front-end. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/'>SQL | DDL, DQL, DML, DCL and TCL Commands</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Dcl |
DCL (Data Control Language): |
||||||
|
|
||||||
|
DCL includes commands such as GRANT and REVOKE which mainly deal with the rights, permissions, and other controls of the database system. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/'>SQL | DDL, DQL, DML, DCL and TCL Commands</BadgeLink> |
||||||
|
|||||||
@ -1 +1,8 @@ |
|||||||
# Locking |
# Locking |
||||||
|
|
||||||
|
Locks are used to prevent data from being modified by multiple processes at the same time. This is important because if two processes are modifying the same data at the same time, the data can become corrupted. Locks are used to prevent this from happening. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://medium.com/inspiredbrilliance/what-are-database-locks-1aff9117c290'>Locking in Databases and Isolation Mechanisms</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.dbta.com/Columns/DBA-Corner/Understanding-Database-Lock-Timeouts-and-Deadlocks-148659.aspx'>Understanding Database Lock Timeouts and Deadlocks</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=nuBi2XbHH18'>Row-Level Database Locks Explained - (Read vs Exclusive)</BadgeLink> |
||||||
|
|||||||
@ -1 +1,8 @@ |
|||||||
# Acid model |
# ACID |
||||||
|
|
||||||
|
ACID are the four properties of any database system that help in making sure that we are able to perform the transactions in a reliable manner. It's an acronym which refers to the presence of four properties: atomicity, consistency, isolation and durability |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink badgeText='Read' colorScheme='yellow' href='https://retool.com/blog/whats-an-acid-compliant-database/'>What is ACID Compliant Database?</BadgeLink> |
||||||
|
<BadgeLink badgeText='Read' colorScheme='yellow' href='https://fauna.com/blog/what-is-acid-compliance-atomicity-consistency-isolation'>What is ACID Compliance?: Atomicity, Consistency, Isolation</BadgeLink> |
||||||
|
<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=yaQ5YMWkxq4'>ACID Explained: Atomic, Consistent, Isolated & Durable</BadgeLink> |
||||||
|
|||||||
@ -1 +1,10 @@ |
|||||||
# Base model |
# BASE Model |
||||||
|
|
||||||
|
The rise in popularity of NoSQL databases provided a flexible and fluidity with ease to manipulate data and as a result, a new database model was designed, reflecting these properties. The acronym BASE is slightly more confusing than ACID but however, the words behind it suggest ways in which the BASE model is different and acronym BASE stands for:- |
||||||
|
|
||||||
|
- **B**asically **A**vailable |
||||||
|
- **S**oft state |
||||||
|
- **E**ventual consistency |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/acid-model-vs-base-model-for-database/'>ACID Model vs BASE Model For Database</BadgeLink> |
||||||
|
|||||||
@ -1 +1,10 @@ |
|||||||
# Cap theorem |
# CAP Theorem |
||||||
|
|
||||||
|
CAP is an acronym for Consistency, Availability, and Partition Tolerance. According to the CAP theorem, any distributed system can only guarantee two of the three properties at any time. You can't guarantee all three properties at once. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.bmc.com/blogs/cap-theorem/'>What is CAP Theorem?</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://en.wikipedia.org/wiki/CAP_theorem'>CAP Theorem - Wikipedia</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://mwhittaker.github.io/blog/an_illustrated_proof_of_the_cap_theorem/'>An Illustrated Proof of the CAP Theorem</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.ibm.com/uk-en/cloud/learn/cap-theorem'>CAP Theorem and it's applications in NoSQL Databases</BadgeLink> |
||||||
|
<BadgeLink colorScheme='purple' badgeText='Watch' href='https://www.youtube.com/watch?v=_RbsFXWRZ10'>What is CAP Theorem?</BadgeLink> |
||||||
|
|||||||
@ -1 +1,7 @@ |
|||||||
# Pacelc theorem |
# PACELC Theorem |
||||||
|
|
||||||
|
The PACELC Theorem is an extension of the CAP Theorem. One of the questions that CAP Theorem wasn’t able to answer was “what happens when there is no Partition, What Logical Combination then a Distributed System have?“. So to answer this, In addition to Consistency, Availability, and Partition Tolerance it also includes Latency as one of the desired properties of a Distributed System. The acronym PACELC stands for Partitioned, Availability, Consistency Else Latency, Consistency. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/pacelc-theorem/'>PACELC Theorem - Geeks for Geeks</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.scylladb.com/glossary/pacelc-theorem/'>PACELC Theorem</BadgeLink> |
||||||
|
|||||||
@ -1 +1,7 @@ |
|||||||
# Indexes |
# Database Indexes |
||||||
|
|
||||||
|
An index is a data structure that you build and assign on top of an existing table that basically looks through your table and tries to analyze and summarize so that it can create shortcuts. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.freecodecamp.org/news/database-indexing-at-a-glance-bb50809d48bd/'>An in-depth look at Database Indexing</BadgeLink> |
||||||
|
<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=-qNSXK7s7_w'>Database Indexing Explained</BadgeLink> |
||||||
|
|||||||
@ -1 +1,8 @@ |
|||||||
# Views |
# Views |
||||||
|
|
||||||
|
Views in SQL are kind of virtual tables. A view also has rows and columns as they are in a real table in the database. We can create a view by selecting fields from one or more tables present in the database. A View can either have all the rows of a table or specific rows based on certain condition. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sql-views/'>SQL | Views</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.ibm.com/docs/en/eamfoc/7.6.0?topic=structure-views'>Datbase Views</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://en.wikipedia.org/wiki/View_(SQL)'>SQL Views - Wikipedia</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Transactions |
# Transactions |
||||||
|
|
||||||
|
In short, a database transaction is a sequence of multiple operations performed on a database, and all served as a single logical unit of work — taking place wholly or not at all. In other words, there's never a case where only half of the operations are performed and the results saved. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://fauna.com/blog/database-transaction'>What are Transactions?</BadgeLink> |
||||||
|
|||||||
@ -1 +1,7 @@ |
|||||||
# Stored procedures |
# Stored Procedures |
||||||
|
|
||||||
|
Stored Procedures are created to perform one or more DML operations on Database. It is nothing but the group of SQL statements that accepts some input in the form of parameters and performs some task and may or may not returns a value. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/what-is-stored-procedures-in-sql/'>What is Stored Procedures in SQL ?</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.programiz.com/sql/stored-procedures'>SQL Stored Procedures</BadgeLink> |
||||||
|
|||||||
@ -1 +1,6 @@ |
|||||||
# Database federation |
# Database Federation |
||||||
|
|
||||||
|
Federation (or functional partitioning) splits up databases by function. The federation architecture makes several distinct physical databases appear as one logical database to end-users. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://dev.to/karanpratapsingh/system-design-the-complete-course-10fo#database-federation'>Database Federation</BadgeLink> |
||||||
|
|||||||
@ -1 +1,7 @@ |
|||||||
# Replication |
# Replication |
||||||
|
|
||||||
|
Replication is a process that involves sharing information to ensure consistency between redundant resources such as multiple databases, to improve reliability, fault-tolerance, or accessibility. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://dev.to/karanpratapsingh/system-design-the-complete-course-10fo#database-replication'>Database Replication</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://en.wikipedia.org/wiki/Replication_(computing)'>Replication (computing)</BadgeLink> |
||||||
|
|||||||
@ -1 +1,9 @@ |
|||||||
# Sharding |
# Sharding |
||||||
|
|
||||||
|
Database sharding is a method of distributing data across multiple machines. It is a horizontal scaling technique, as opposed to vertical scaling, which is scaling by adding more power to a single machine. Sharding is a common way to scale a database. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://dev.to/karanpratapsingh/system-design-the-complete-course-10fo#sharding'>Sharding</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=RynPj8C0BXA'>Sharding & Database Partitioning | System Design Basics</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=hdxdhCpgYo8'>Database Sharding - Watch</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=kSH4bt8ypOQ'>Database Sharding in 5 minutes</BadgeLink> |
||||||
|
|||||||
@ -1 +1,8 @@ |
|||||||
# Databases |
# Databases |
||||||
|
|
||||||
|
A database is a collection of useful data of one or more related organizations structured in a way to make data an asset to the organization. A database management system is a software designed to assist in maintaining and extracting large collections of data in a timely fashion. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.oracle.com/database/what-is-database/'>Oracle: What is a Database?</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.prisma.io/dataguide/intro/what-are-databases'>Prisma.io: What are Databases?</BadgeLink> |
||||||
|
<BadgeLink colorScheme='red' badgeText='Watch' href='https://www.youtube.com/watch?v=D-k-h0GuFmE&list=PL9ysvtVnryGpnIj9rcIqNDxakUn6v72Hm'>DBMS by Stanford</BadgeLink> |
||||||
|
|||||||
Loading…
Reference in new issue