Skip to content

Commit f70c07c

Browse files
authored
Merge pull request #30 from ShashaankS/INTRO-DBaaS-learning-path
Intro DBaaS Learning Path
2 parents 87a1e21 + b93be54 commit f70c07c

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+430
-0
lines changed
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: "INTRO DBaaS"
3+
description: "This INTRO DBaaS - Learning Paths covers the foundational topics of DBaaS for a non-technical audience and conveys the benefits of data services and databases as a service for modern IT scenarios. It will help you learn the basics of terminology associated, understand the essential components' functions, and why these new technologies are so important."
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
courses: 3
7+
weight: 3
8+
---
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: "Why Databases?"
3+
description: ""
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
courses: 7
7+
weight: 1
8+
---
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
docType: "Chapter"
3+
id: "Benefits of Databases"
4+
chapterTitle: "Benefits of Databases"
5+
description: ""
6+
title: "Benefits of Databases"
7+
weight: 6
8+
---
9+
10+
### **Benefits of Databases**
11+
12+
![db-icon-1]({{< usestatic "intro-dbaas/db-icon-1.png" >}})
13+
14+
#### **Why use computerized Databases?**
15+
16+
Because it makes it easier to:
17+
- sort data
18+
- search and find data
19+
- add, edit or delete data
20+
- store large data sets efficiently
21+
- access data at the same time by multiple users
22+
- import and export data from and to other applications
23+
24+
If there are advantages, then there are also disadvantages, and to get a complete picture of the database situation, let us contrast them.
25+
26+
![db-icon-2]({{< usestatic "intro-dbaas/db-icon-2.png" >}})
27+
28+
#### **Advantages of Databases:**
29+
30+
- Data Sharing
31+
- Data Security
32+
- Data Abstraction
33+
- Concurrent Access
34+
- Easy Data Manipulation
35+
- Support Multi-User Views
36+
- Data Redundancy Controlling
37+
- Data Inconsistency Minimizing
38+
39+
![db-icon-3]({{< usestatic "intro-dbaas/db-icon-3.png" >}})
40+
41+
#### **Disadvantages of Databases:**
42+
43+
- Cost of Software
44+
- Cost of Hardware
45+
- Cost of Staff Training
46+
- Cost of Data Conversion
47+
- Complexity of High Availability
48+
- Complexity of Backup & Restore
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
docType: "Chapter"
3+
id: "Data"
4+
chapterTitle: "Data"
5+
description: ""
6+
title: "Data"
7+
weight: 1
8+
---
9+
10+
### **Data**
11+
12+
Data is the fuel of our society. Can we agree on that? There were many bold statements over the years to underline the importance of data. Data is the new oil; Data is the new gold; all variations you have probably come across if you follow the news, media, or social media. Data is the new water - is a fresh analogy you can find in researching the data topic.
13+
14+
" Like water, data needs to be accessible, it needs to be clean, and it is needed to survive." - Dan Vesset (IDC)
15+
16+
17+
![cloud]({{< usestatic "intro-dbaas/data-word-cloud.png" >}})
18+
19+
*Data Word Cloud*
20+
21+
The water analogy is probably more appealing because we should be more fond of water than gold or oil for many reasons, but it is pretty evident from a pure survival point of view.
22+
We are getting back to our core topic data and databases. The collection of (important) data in the past and storing it in databases for reuse and archiving it for preservation is as old as humanity. For example, the Sumerians already used clay tablets to keep the index of medical prescriptions as a form of database, so databases started long before computers were even invented.
23+
The increase in the volume of data we produce every year has reached an almost frightening value. The digital revolution induces the reason for this exponential increase in data production. Keeping track and oversight in this data situation, we have to improve and invent new data tools, or otherwise, we would get lost in data.
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
docType: "Chapter"
3+
id: "History of Databases"
4+
chapterTitle: "History of Databases"
5+
description: ""
6+
title: "History of Databases"
7+
weight: 5
8+
---
9+
10+
### **History of Databases**
11+
12+
**Part 1** of the History of Database Evolution covers the events until the initiation of an industry around database technologies. This was also illustrated in the last unit and the linked History of Databases YouTube video.
13+
14+
15+
![history-part-1]({{< usestatic "intro-dbaas/history-part-1.png" >}})
16+
17+
**Part 2** of the History of Database Evolution is about the influence of new technologies and the emergence of new players with new clever ideas (new database models). Today is all about combining, improving, optimizing, and automizing all available database models and their respective implementations (closed source and open source). The future is focused on driving business innovations with specialized database models specifically built/developed for business requirements.
18+
19+
20+
![history-part-2]({{< usestatic "intro-dbaas/history-part-2.png" >}})
21+
22+
A glimpse of the future can be found in this excellent wired.com blog post infographic from approx. 2016 (The Future of the Database -- © wired.com). Unfortunately, the article is not available anymore, but the graphic survived on the internet. It gives an excellent summary of the past and predicts the future, as seen in 2016.
23+
24+
![history-part-3]({{< usestatic "intro-dbaas/future-of-dbs.png" >}})
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
docType: "Chapter"
3+
id: "Selection of Databases"
4+
chapterTitle: "Selection of Databases"
5+
description: ""
6+
title: "Selection of Databases"
7+
weight: 7
8+
---
9+
10+
### **Selection of Databases**
11+
12+
The prolific database situation makes the pick of a particular technology not easy. Many theorems, models, and concepts support that selection process, meaning no universal solution for database choices is available.
13+
14+
![selection]({{< usestatic "intro-dbaas/selection.png" >}})
15+
16+
The CAP theorem gives guidance and is still relevant when designing distributed applications and choosing a data store for such scenarios. Still, you have to decide if availability is the preference or consistency gets the vote.
17+
18+
![CAP]({{< usestatic "intro-dbaas/CAP.png" >}})
19+
20+
Due to the broad spectrum of database types, a different approach for selecting the right technology for the data store is to choose based on the kind of data that needs storage. Let’s have a look at some examples:
21+
22+
#### **Managed PostgreSQL**
23+
![dbaas-pg]({{< usestatic "intro-dbaas/dbaas-pg.png" >}})
24+
25+
PostgreSQL is a popular open source relational database known for its variety of features. It supports both SQL and JSON querying. The database offers a high level of integrity, correctness, and reliability. Rich features like MVCC, point in time recovery and asynchronous replication are part of the PostgreSQL database. You find more details about this database here.
26+
27+
#### **Managed MySQL**
28+
![dbaas-mysql]({{< usestatic "intro-dbaas/dbaas-mysql.png" >}})
29+
30+
MySQL is the most widely used open source, object-relational database. It serves as a primary database for many known applications and is well known for its reliability and stability. MySQL has a very active developer community that continuously expand the MySQL functionalities. You find more details about this database here.
31+
32+
#### **Managed Apache Kafka**
33+
![dbaas-kafka]({{< usestatic "intro-dbaas/dbaas-kafka.png" >}})
34+
35+
Apache Kafka is a distributed, open source data source optimized for real-time processing of streaming data. The database enables low latency due to decoupled data streams, which makes it extremely high performing. Apache Kafka is highly scalable thanks to its distributed nature and makes it easily scalable. You find more details about this database here.
36+
37+
#### **Managed Redis™**
38+
![dbaas-redis]({{< usestatic "intro-dbaas/dbaas-redis.png" >}})
39+
40+
Redis™ is an open source, key-value data store used as database, cache or message broker. The in-memory dataset allows for top performance, making it a good choice for caching, session management or real-time analytics. Redis™ supports atomic operations, rich data types, and Lua scripting. You find more details about this database here.
41+
42+
#### **Managed OpenSearch**
43+
![dbaasopensearch]({{< usestatic "intro-dbaas/dbaas-opensearch.png" >}})
44+
45+
OpenSearch is a community-driven, open source search and analytics suite derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It consists of a search engine daemon, OpenSearch, and a visualization and user interface, OpenSearch Dashboards. OpenSearch enables people to easily ingest, secure, search, aggregate, view, and analyze data. You find more details about this database here.
46+
47+
#### **Managed OpenSearch**
48+
49+
For example, are you dealing with structured or unstructured data, or do you have a mixed data environment?
50+
51+
![spectrum]({{< usestatic "intro-dbaas/spectrum.png" >}})
52+
53+
Is one database technology sufficient to provide the functionality, or is it a blend of database technologies that deliver the solution?
54+
55+
![scenario]({{< usestatic "intro-dbaas/scenario.png" >}})
56+
57+
Guidance is challenging to find, especially if you want to see the complete picture of available technology offers and not choosing a vendor first and then picking what is available in the portfolio.
58+
59+
![book]({{< usestatic "intro-dbaas/book.png" >}})
60+
61+
Fortunately, a book supports in a very structured way with a map of all the relevant topics this vital selection process—this desired holistic approach to data store selection for data-intensive applications is a source of wisdom.
62+
63+
![structure]({{< usestatic "intro-dbaas/structure.png" >}})
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
docType: "Chapter"
3+
id: "Tools for Data"
4+
chapterTitle: "Tools for Data"
5+
description: ""
6+
title: "Tools for Data"
7+
weight: 4
8+
---
9+
10+
### **Tools for Data**
11+
12+
![db-cloud]({{< usestatic "intro-dbaas/db-word-cloud.png" >}})
13+
14+
*Database Word Cloud*
15+
16+
Using databases to organize data started long before the age of computers. Sumerian clay tablets, ship manifests, card catalogs, and product inventories are all databases. Computers enabled the automation of databases. For computer-based databases, we have to distinguish the database model from the software implementation of that model.
17+
18+
The first database model in the computer era was the Flat File Model, a simple consecutive list of records that mimicked the non-computational model from the past as card catalogs or ship manifests. In the mid-1960s, IBM developed a hierarchical database model for their software solution called IMS (Information Management System), which was debuted in 1968 and supported NASA's Moon Mission efforts.
19+
20+
![CHM]({{< usestatic "intro-dbaas/CHM.png" >}})
21+
22+
*Computer History Museum - Databases*
23+
24+
The Dawn of the Database as we know it today was initiated in 1970 by Ted Codd, a computer scientist at IBM. A relational database model organized the data in simple tables, making it easier to access, merge, and change. In hindsight, this was the game-changer, and the seed from that grew an entirely new industry. The idea was picked up by academia first (UC Berkley) and enterprises later to release new software products based on the new relational database model. Even IBM started implementing an experimental solution called System R in 1975.
25+
26+
If you want to know the entire history with more details, you can watch it (History of Databases by Computer History Museum) on YouTube in less than six minutes [here](https://www.youtube.com/watch?v=KG-mqHoXOXY). A quick structured overview of the History of the Database Evolution is put together in the next unit.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
docType: "Chapter"
3+
id: "Value Chain of Data"
4+
chapterTitle: "Value Chain of Data"
5+
description: ""
6+
title: "Value Chain of Data"
7+
weight: 3
8+
---
9+
10+
### **Value Chain of Data**
11+
12+
"Like water, data needs to be accessible, it needs to be clean, and it is needed to survive." - Dan Vesset (IDC)
13+
14+
![value-of-data-1]({{< usestatic "intro-dbaas/value-of-data-1.png" >}})
15+
16+
We looked at the importance of data and want to briefly cover the last introduction aspect relevant to our database and database as a service journey. If you break down the diagram above, you see two significant aspects of data interactions. Production of data and usage of data, those two categories are further divided into collection and publication on the left-hand side and uptake and impact on the right-hand side.
17+
18+
Relevance? Think about the tools and the required features to address those tasks effectively and efficiently, keep on thinking, and factor in scalability, availability, and performance. These are all traits of good data handling tools, and there are prominent examples of very successful companies out there who mastered that data value endeavor perfectly.
19+
20+
![value-of-data-2]({{< usestatic "intro-dbaas/value-of-data-2.png" >}})
21+
22+
Look at Uber and Airbnb and how they successfully challenged their respective industries with an approach based on data, software solutions, and a customer-first mindset focused on convenience. And convenience always wins.
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
docType: "Chapter"
3+
id: "Volume of Data"
4+
chapterTitle: "Volume of Data"
5+
description: ""
6+
title: "Volume of Data"
7+
weight: 2
8+
---
9+
10+
### **Volume of Data**
11+
12+
Statista provides incredible insights into our world via the looking glass of statistics. The mind-boggling statistic about the created volume of data we make worldwide every year can be found just below this paragraph.
13+
14+
![volume-of-data]({{< usestatic "intro-dbaas/volume-of-data.png" >}})
15+
16+
You can quickly see that the amount of data we produce every year doubled, tripled, or even quadrupled in the last years. Depending on how many years you look back, the internet, the smartphone, social media, digital photography, digital music, digital films, and the Internet of Things, to name a few of the contributors to this enormous peak in the growth of data.
17+
18+
However, if we look beyond today's development, it's even more shocking or astonishing. But what the heck are zettabytes? The majority is undoubtedly familiar with Megabyte, Gigabyte, and if you are into digital photography or video making Terabyte. But then we still have to jump further powers of ten - Petabytes and Exabytes - to reach the Zettabytes. Zettabyte equals 1.000.000.000.000.000.000.000 bytes, yes 21 zeros.
19+
20+
It is difficult to grasp this amount of data. Therefore, follow the experiment of visualizing this enormous data volume and setting it into relation to something that could demonstrate Zettabytes' monstrosity. The diagram below uses floppy disks from the digital old age and the solar system as a size reference to make the experiment work.
21+
22+
The figure the statistic gave us was 79 Zettabytes in 2021. In 2021 the world population is stated as 7.9 billion people. This means; statistically, every person on the planet is creating 10 Terabyte of data in 2021. But, what if we would store all the 79 Zettabytes on good old Floppy Disks? How high, or how long would this stack be?
23+
24+
![zettabyte]({{< usestatic "intro-dbaas/zettabyte.png" >}})
25+
26+
As you can see, the stack out of Floppy Disks in the diagram is pretty BIG. Our solar system expands 4.5 billion km into space there, and you can find the last planet, Neptune. But the stack of Floppy Disks would go on and finally point 181 billion km into space. There is nothing exceptional there, and in terms of interstellar travel, this is a short trip, but we would never get there in a lifetime with the means of transportation available today. All these astronomical facts and figures aside, the horror of Zettabytes starts probably taking shape in your mind now.
27+
28+
A long and diverting intro for an IT topic like databases, but as we have seen, storing data is an old topic. Moreover, depending on the volume of data, the evolution of the data tools is becoming essential. Hence, database technology is evergreen in information technology.
29+
30+
Before we jump into the database topic, let's explore one last important facet of data today, the data value chain and companies based on data.
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: "Why Exoscale DBaaS?"
3+
description: ""
4+
themeColor: "#3C494F"
5+
cardImage: "/images/learning-path/kubernetes-icon.svg"
6+
courses: 3
7+
weight: 3
8+
---

0 commit comments

Comments
 (0)