Welcome to the Certified Data Architecture Expert program! This advanced certification is designed for experienced data professionals who want to master the art and science of designing, building, and governing enterprise-scale data systems. Building on foundational knowledge, this program dives deep into complex architectures, strategic planning, and cutting-edge technologies.
Data is the lifeblood of modern organizations, and expert data architects are the master planners who design the systems that manage this critical asset. This course will equip you with the skills to architect robust, scalable, secure, and intelligent data platforms that drive business innovation.
The program is structured into 8 comprehensive modules, combining deep theoretical foundations with extensive hands-on labs, case studies, and a capstone project that simulates a real-world enterprise transformation.
| Detail | Information |
|---|---|
| Program Title | Certified Data Architecture Expert |
| Target Audience | Senior Data Architects, Lead Data Engineers, Enterprise Architects, CTOs, Heads of Data |
| Prerequisites | Certified Data Architecture Specialist or equivalent experience |
| Duration | Flexible – typically 3–6 months (depending on pace) |
| Format | Online / In-person / Blended with hands-on labs |
| Certification | Official certification upon completion of capstone project |
Why become a Certified Data Architecture Expert?
The program consists of 8 core modules, each building on the previous one. The course culminates in a capstone project where you will design and implement a complete enterprise data architecture for a real-world scenario.
Overview: This module builds upon foundational concepts, exploring advanced principles, frameworks, and strategic considerations for enterprise data architecture.
Learning Outcomes:
Overview: This module provides an in-depth exploration of modern data storage technologies, including distributed systems, database engineering, and performance optimization.
Learning Outcomes:
Overview: This module explores sophisticated data modeling techniques for complex enterprise scenarios, including dimensional modeling, data vault, and modern modeling approaches.
Learning Outcomes:
Overview: This module covers advanced data integration techniques, including streaming, event-driven, and hybrid integration patterns.
Learning Outcomes:
Overview: This module explores the cutting-edge paradigms of data mesh and data fabric, enabling decentralized data ownership and seamless data connectivity across the enterprise.
Learning Outcomes:
Overview: This module focuses on designing data architectures that support AI/ML workloads, including data pipelines, feature stores, model deployment, and monitoring.
Learning Outcomes:
Overview: This module provides deep expertise in enterprise data governance, data security, and regulatory compliance, including emerging areas like AI governance.
Learning Outcomes:
Overview: This module focuses on the strategic, leadership, and business aspects of data architecture – essential for senior roles.
Learning Outcomes:
Overview: The capstone project is the culmination of your learning journey. You will design a complete enterprise data architecture for a complex organization, integrating all the concepts you have learned.
Project Scope:
Outcome: You will create a comprehensive, portfolio-ready project that demonstrates your expertise as a Certified Data Architecture Expert.
Assessment Methods:
Certification:
| Term | Definition |
|---|---|
| Data Mesh | A decentralized data architecture that treats data as a product, with domain-oriented ownership. |
| Data Fabric | An architecture that connects data across different environments with a unified layer. |
| Data Vault 2.0 | A data modeling methodology for enterprise data warehousing that supports agility and scalability. |
| Data Lakehouse | A hybrid architecture combining the scalability of data lakes with the performance of data warehouses. |
| MLOps | Machine Learning Operations – practices for managing the ML lifecycle. |
| Feature Store | A centralized repository for storing and serving features for ML models. |
| Zero-Trust Architecture | A security model that assumes no trust and verifies every access request. |
| Data Governance | The management of data availability, usability, integrity, and security. |
| Data Lineage | Tracking the flow of data from source to destination, including transformations. |
| Data Product | A data asset that is treated as a product with a clear owner, SLA, and user focus. |
This program is designed for senior professionals. Use case studies, real-world examples, and guest lectures from industry experts. Emphasize strategic thinking, leadership, and practical application. The capstone project should be a significant piece of work that demonstrates mastery of all concepts.
If you are supporting a learner in this program, encourage them to think about how data architecture affects the world around them – from banking to healthcare. Discuss the importance of data governance and security. Celebrate their achievements as they become experts in the field.
+---------------------------------------+
| Data Mesh |
+---------------------------------------+
| +--------+ +--------+ +--------+ |
| | Sales | | Marketing| | Finance| |
| | Domain | | Domain | | Domain | |
| +--------+ +--------+ +--------+ |
| | | | |
| +-----------+-----------+ |
| | |
| +--------+--------+ |
| | Self-Serve Data | |
| | Infrastructure | |
| +--------+--------+ |
| | |
| +--------+--------+ |
| | Federated | |
| | Governance | |
| +-----------------+ |
+---------------------------------------+
+---------------------------------------+
| Data Fabric |
+---------------------------------------+
| +--------+ +--------+ +--------+ |
| | Cloud | | On-prem| | Edge | |
| | Data | | Data | | Data | |
| +--------+ +--------+ +--------+ |
| | | | |
| +-----------+-----------+ |
| | |
| +--------+--------+ |
| | Active Metadata | |
| | Management | |
| +--------+--------+ |
| | |
| +--------+--------+ |
| | Data Virtualization| |
| | Semantic Layer | |
| +--------+--------+ |
+---------------------------------------+
| Feature | Data Mesh | Data Fabric |
|---|---|---|
| Focus | Decentralized ownership, data products | Unified connectivity, integration |
| Goal | Agility, scalability, domain ownership | Seamless data access, reduced integration costs |
| Key Components | Domains, data products, self-serve infrastructure, federated governance | Active metadata, virtualization, semantic layer, connectors |
| Best For | Large organizations with multiple domains | Organizations with diverse data sources and environments |
The Certified Data Architecture Expert program provides a comprehensive pathway to mastering enterprise data architecture. You will gain deep expertise in data mesh, data fabric, AI/ML data architecture, governance, security, and strategic leadership.
This program is designed for experienced professionals who are ready to take on the most challenging data architecture roles. You will be equipped to lead enterprise-wide data initiatives and drive business transformation through data.
Take the next step in your career – become a Certified Data Architecture Expert!
Before starting the Certified Data Architecture Expert program, we recommend:
The world of enterprise data architecture is waiting for you – take the next step!
Hello, future Data Architect! Welcome to the first module of your journey to become a Certified Data Architecture Specialist. You might be wondering: "What is data?" and "Why does it matter?"
Think about your favorite video game. Every time you play, the game remembers your level, your score, and the items you collected. How does it do that? It uses data! Data is just information that computers store and use.
In this module, we will learn what data is, where it comes from, and how it is stored. We will use simple stories and examples so that even a 10-year-old can understand. By the end, you will see data everywhere – in your games, your schoolwork, and even in the market!
Let's begin our adventure with a fun story.
After this module, you will be able to:
Ada loved helping her mother at the market in Lagos. Every day, her mother sold fruits and vegetables. But there was a problem – her mother could not remember how many apples she had or how much money she made.
Ada had an idea. She took a small notebook and started writing things down. She wrote:
Now Ada's mother could see exactly what she sold and how much money she made. The notebook was full of data – numbers and words that told a story.
Ada realised that data is like a treasure – when you collect it and organise it, it becomes information that helps you make better decisions.
Now, let's learn more about this amazing thing called data!
Definition: Data is any collection of facts, numbers, words, or pictures that can be stored and used by a computer.
Why is it important? Without data, computers would be empty boxes – they would not know anything!
Simple explanation: Data is like ingredients for a recipe. Just like you need flour, sugar, and eggs to bake a cake, computers need data to do their jobs.
Real‑life example: Your name, your age, and your favorite color are all pieces of data.
School example: Your test scores are data. The teacher uses them to know how you are doing.
Home example: The list of groceries your parents buy is data.
Nigerian example: The price of tomatoes at the market is data.
Illustration:
+---------------------+
| Data = Facts |
| - "Ada" (name) |
| - 10 (age) |
| - 500 (naira) |
+---------------------+
Mini summary: Data is just facts – numbers, words, or pictures that computers can store and use.
Definition: Data is raw facts. Information is data that has been organised and given meaning.
Why is it important? Data is like puzzle pieces. Information is the complete picture you see after putting the pieces together.
Simple explanation: "10, 15, 20" is data. "Ada sold 10 apples today" is information because it tells you something useful.
Real‑life example: The number "37" is data. "Your body temperature is 37 degrees Celsius" is information.
School example: A list of grades (85, 90, 78) is data. "You got an A in Math" is information.
Home example: A list of groceries (milk, bread, eggs) is data. "We need to buy milk and bread for breakfast" is information.
Nigerian example: "500 naira" is data. "You spent 500 naira on transport this week" is information.
Illustration:
Data: 10, 15, 20
Information: "Ada sold 10 apples, 15 oranges, and 20 bananas."
Mini summary: Data is raw; information is data that has been organised to mean something.
Definition: Data comes in many forms – numbers, text, pictures, sounds, and even videos!
Why is it important? Different types of data are used for different purposes. You can't add words together like numbers!
Simple explanation: Think of data like different kinds of toys – you have building blocks, dolls, and balls. Each is different and used in its own way.
Real‑life example: Your phone contacts list has text (names) and numbers (phone numbers).
School example: Your textbook has text (words) and pictures (diagrams).
Home example: A recipe has text (instructions), numbers (quantities), and pictures (photos of the dish).
Nigerian example: A market stall has prices (numbers), product names (text), and pictures (advertising).
Illustration:
+------------------+------------------+------------------+
| Numbers | Text | Pictures |
| 10, 20, 500 | "Hello", "Ada" | 🍎 🍊 🍌 |
+------------------+------------------+------------------+
Mini summary: Data can be numbers, text, pictures, sounds, and more!
Definition: Data comes from many places – people, sensors, computers, and even the internet.
Why is it important? Knowing where data comes from helps us understand if it is reliable and useful.
Simple explanation: Data is like raindrops – they come from clouds (sources) and fall to the ground (where we collect them).
Real‑life example: When you fill out a form online, you are creating data.
School example: When your teacher takes attendance, they are collecting data.
Home example: A smart thermostat collects data about the temperature in your home.
Nigerian example: A POS machine collects data about transactions.
Illustration:
Sources of Data:
+---------+ +---------+ +---------+
| People | | Sensors | | Computers|
+----+----+ +----+----+ +----+----+
| | |
+-------------+--------------+
|
v
+-------------+
| Data |
+-------------+
Mini summary: Data comes from people, machines, and other computers.
Definition: Computers need data to do anything useful. Without data, they are just machines that do nothing.
Why is it important? Data is the "food" that computers need to work.
Simple explanation: Think of a computer like a chef. Without ingredients (data), the chef cannot cook anything.
Real‑life example: A weather app on your phone needs data from weather sensors to show you the forecast.
School example: A school grading system needs student scores (data) to calculate grades.
Home example: A smart TV needs data from the internet to stream movies.
Nigerian example: A banking app needs transaction data to show your balance.
Illustration:
Computer + Data = Useful Program
(Chef) + (Ingredients) = (Delicious Meal)
Mini summary: Data is the fuel that makes computers useful.
Definition: Businesses use data to make better decisions, understand their customers, and improve their products.
Why is it important? Data helps businesses grow and succeed.
Simple explanation: Data is like a map for a business – it shows where to go and what to do.
Real‑life example: A shop owner uses sales data to know which products are popular.
School example: A school uses attendance data to identify students who need help.
Home example: You use a shopping list (data) to know what to buy.
Nigerian example: A market trader uses data to know which items sell best.
Illustration:
+---------------------+
| Data → Decision |
| Sales data → Stock |
| Customer data → Ads |
+---------------------+
Mini summary: Businesses use data to make smart decisions.
Definition: Data is stored in many ways – on paper, in computers, on the cloud, and even in the memory of devices.
Why is it important? Storing data allows us to use it later, just like writing notes in a notebook.
Simple explanation: Storing data is like putting toys in a toy box – you can take them out later to play.
Real‑life example: Your photos are stored on your phone's memory.
School example: Your grades are stored in the school's computer system.
Home example: Your family's recipes are stored in a notebook.
Nigerian example: A bank stores your account information in their computers.
Illustration:
Storage Media:
+---------+ +---------+ +---------+
| Hard Disk| | Cloud | | Paper |
+----+----+ +----+----+ +----+----+
| | |
+-------------+--------------+
|
v
+-------------+
| Data |
+-------------+
Mini summary: Data can be stored on paper, computers, and the cloud.
Definition: A data architect is a person who designs how data is stored, organised, and used in a company.
Why is it important? A good data architect makes sure that data is easy to find, secure, and useful.
Simple explanation: Think of a data architect as a librarian – they organise the books (data) so that people can find what they need quickly.
Real‑life example: A data architect designs the system that stores all the data for a big company like Jumia.
School example: A school librarian organises books so students can find them.
Home example: You organise your closet – clothes in one section, shoes in another.
Nigerian example: A data architect designs the system that stores NIN (National Identification Number) data.
Illustration:
Data Architect
|
v
+-----------------+
| Organises Data |
| Keeps it Safe |
| Makes it Easy |
+-----------------+
Mini summary: A data architect designs systems to store and manage data.
Definition: Data quality means that data is accurate, complete, and reliable.
Why is it important? Bad data leads to bad decisions. If your data is wrong, your decisions will be wrong too.
Simple explanation: If you use the wrong ingredients to bake a cake, the cake will not taste good. Data works the same way.
Real‑life example: If a weather app uses bad data, it will give you the wrong forecast.
School example: If your teacher writes the wrong grade, you will think you did worse than you actually did.
Home example: If your shopping list says "milk" but you meant "bread", you will buy the wrong item.
Nigerian example: If a bank has wrong data, they might give you too much or too little money.
Illustration:
Good Data → Good Decision
Bad Data → Bad Decision
Mini summary: Good data quality means data is correct and complete.
Definition: Data security means protecting data from being stolen, lost, or damaged.
Why is it important? If data is stolen, people's privacy can be harmed.
Simple explanation: Data security is like locking your house – you want to keep bad people out.
Real‑life example: Banks use passwords and encryption to protect your money data.
School example: Your school uses passwords to keep your grades private.
Home example: You lock your phone with a PIN to keep your photos private.
Nigerian example: The NIN system uses security to protect your personal information.
Illustration:
+---------------------+
| Data Security |
| +--+--+--+--+--+ |
| | Passwords | |
| | Encryption | |
| | Backups | |
| +-----------------+ |
+---------------------+
Mini summary: Data security keeps information safe from theft and loss.
Definition: The cloud is a network of computers that store and process data over the internet.
Why is it important? The cloud allows us to store data anywhere and access it from any device.
Simple explanation: The cloud is like a giant, invisible hard drive that you can use from anywhere.
Real‑life example: Google Drive, iCloud, and OneDrive are all cloud storage services.
School example: Your school uses cloud storage to save assignments and projects.
Home example: You store photos in the cloud so you can see them on any device.
Nigerian example: Many Nigerian companies use cloud services to store their data.
Illustration:
Your Device → Internet → Cloud Servers
(Phone) → (Wi-Fi) → (Data Storage)
Mini summary: The cloud is a way to store data on the internet so you can access it anywhere.
Definition: Big data is very large amounts of data that are too big for normal computers to handle.
Why is it important? Big data can reveal patterns and trends that help businesses and governments make decisions.
Simple explanation: If you have a few marbles, you can count them easily. If you have millions of marbles, you need a special machine to count them. That's big data.
Real‑life example: Social media companies like Facebook and Twitter collect huge amounts of data every day.
School example: A school with 10,000 students collects a lot of data about attendance and grades.
Home example: A smart home with many sensors collects data about temperature, light, and movement.
Nigerian example: The NIN database has data for millions of Nigerians – that's big data.
Illustration:
Small Data: 10 items
Big Data: 1,000,000 items
Mini summary: Big data is data that is too large for normal computers to process easily.
Definition: The data lifecycle is the journey of data from when it is created to when it is deleted.
Why is it important? Understanding the lifecycle helps us manage data properly.
Simple explanation: Data is born, lives, and eventually dies – just like a plant.
Real‑life example: A customer order is created, processed, and then archived.
School example: A student's records are created when they join, updated each term, and deleted when they leave.
Home example: You create a grocery list, use it, and then throw it away.
Nigerian example: A bank creates a customer account, updates it, and closes it when the customer leaves.
Illustration:
+---------+ +---------+ +---------+ +---------+
| Create | → | Store | → | Use | → | Delete |
+---------+ +---------+ +---------+ +---------+
Mini summary: Data goes through a lifecycle – creation, storage, use, and deletion.
Definition: Data architecture is the overall design of how data is stored, organised, and used in a company.
Why is it important? A good data architecture makes it easy to find, use, and protect data.
Simple explanation: Data architecture is like the blueprint of a house – it shows where everything goes.
Real‑life example: A company's data architecture includes databases, data lakes, and data pipelines.
School example: A school's data architecture includes the student database, the teacher database, and the grading system.
Home example: Your home's data architecture might include your computer, your phone, and your smart TV – all connected.
Nigerian example: The NIN system has a data architecture that stores information for millions of Nigerians.
Illustration:
+---------------------------------------+
| Data Architecture |
+---------------------------------------+
| +---------+ +---------+ +-----+ |
| | Database| | Data Lake| | APIs| |
| +---------+ +---------+ +-----+ |
+---------------------------------------+
Mini summary: Data architecture is the design of how data is stored and used.
Definition: Data affects almost every part of our lives – from the weather app to online shopping to healthcare.
Why is it important? Understanding data helps you make better decisions and understand the world around you.
Simple explanation: Data is everywhere – the more you know about it, the smarter you become.
Real‑life example: When you shop online, data helps recommend products you might like.
School example: Data helps teachers know which students need extra help.
Home example: Data from your smart watch helps you track your health.
Nigerian example: Data helps farmers know when to plant crops and when to sell them.
Illustration:
Data is Everywhere!
+---------+ +---------+ +---------+
| School | | Market | | Health |
+---------+ +---------+ +---------+
| | |
+-------------+--------------+
|
v
+-------------+
| Data |
+-------------+
Mini summary: Data is everywhere and affects our daily lives.
| Word | Simple Definition |
|---|---|
| Data | Facts, numbers, words, or pictures that can be stored. |
| Information | Data that has been organised and has meaning. |
| Data Quality | How accurate and complete data is. |
| Data Security | Keeping data safe from theft or loss. |
| Cloud | Storing data on the internet instead of your own computer. |
| Big Data | Very large amounts of data that are hard to process. |
| Data Architect | A person who designs how data is stored and used. |
| Data Lifecycle | The journey of data from creation to deletion. |
| Data Architecture | The design of how data is stored and used. |
| Encryption | Scrambling data so only authorised people can read it. |
This module is an introduction to data – the foundation of data architecture. Use lots of real-world examples and encourage students to think about data in their daily lives. The goal is to build curiosity and understanding. Ask questions like "Where does this data come from?" and "Why is it important?" to encourage critical thinking.
Encourage your child to identify data in their daily life – at home, at school, and in the market. Discuss where data comes from and why it is important. Help them understand the difference between data and information. Celebrate their curiosity and encourage them to ask questions.
| Type | Example | Used For |
|---|---|---|
| Numbers | 10, 20, 500 | Counting, measuring |
| Text | "Hello", "Ada" | Names, descriptions |
| Pictures | 🖼️ | Visual information |
| Sound | 🎵 | Music, voice |
+---------+ +---------+ +---------+ +---------+
| Create | → | Store | → | Use | → | Delete |
+---------+ +---------+ +---------+ +---------+
+---------------------+
| Data Security |
+---------------------+
| Passwords |
| Encryption |
| Backups |
| Access Control |
| Firewalls |
+---------------------+
You have completed Module 1 – "What is Data?" You have learned that data is the foundation of everything computers do. Data can be numbers, text, pictures, or sounds. You learned the difference between data and information, and why data quality and security are so important.
You also discovered the role of a data architect – someone who designs how data is stored and used. This is the start of your journey to becoming a Certified Data Architecture Specialist!
Well done – you are now ready for Module 2!
| Term | Definition |
|---|---|
| 1. Data | A. Data that has meaning |
| 2. Information | B. Raw facts |
| 3. Data Quality | C. Keeping data safe |
| 4. Data Security | D. How accurate data is |
| 5. Data Architect | E. A person who designs data systems |
Answers: 1‑B, 2‑A, 3‑D, 4‑C, 5‑E
Scenario 1: Ada's mother runs a fruit shop. She wants to know which fruits sell the most. What data should she collect? How should she organise it to get useful information?
Scenario 2: A school wants to improve student performance. They have data about attendance and grades. How can they use this data to make better decisions?
In groups, choose a topic – e.g., "a market stall", "a school", or "a hospital". Discuss what data this place would collect. Write down at least 5 pieces of data and explain why they are important. Present your findings to the class.
Think about your daily routine. What data do you create? For example, the time you wake up, what you eat for breakfast, or how many steps you walk. Write down 5 pieces of data and explain how they could be useful.
Build a Simple Data Collection System: Choose a topic – e.g., "What fruits do my classmates like?" Design a way to collect data (survey), organise it (table), and present the information (chart). This is what data architects do!
Write a report about the data you collect in your daily life. Include at least 5 examples of data, explain where they come from, and describe how they could be used. This will help you practice thinking like a data architect.
Think about a Nigerian business – e.g., a market stall, a bank, or a transport company. Identify the data they collect, how they store it, and how they use it. Write a short essay describing the data architecture of this business.
Fill‑in‑the‑Blank: 1. Data, 2. Information, 3. types, 4. sensors, 5. Data quality, 6. Data security, 7. cloud, 8. Big data, 9. data architect, 10. data lifecycle.
True/False: 1F, 2T, 3F, 4T, 5F, 6T, 7F, 8T, 9T, 10F.
Multiple Choice: 1B, 2B, 3D, 4D, 5B, 6B, 7B, 8B, 9A, 10A, 11A, 12A, 13D, 14A, 15B.
In Module 2, you will learn about data storage – how data is kept in databases, data lakes, and data warehouses. You will also learn about different types of databases and when to use each one. To prepare, think about where you see data being stored in your daily life – on your phone, in the cloud, or in a notebook!
Great work, future Data Architect! See you in Module 2!
Hello again, future Data Architect! In Module 1, you learned what data is and why it is important. Now, we are going to explore where data is stored and how it is organised. Just like you have different places to store your things – a drawer for clothes, a shelf for books, and a box for toys – computers have different places to store data.
In this module, you will learn about databases, data lakes, and data warehouses. These are like special containers that hold data. You will also learn about different ways to organise data so that it is easy to find and use.
Let's begin with a story that will help you understand these ideas!
After this module, you will be able to:
Chidi loved collecting toys. He had cars, action figures, and building blocks. But his room was a mess – toys were everywhere! He could never find what he wanted.
His mother said: “Chidi, you need to organise your toys. Use different boxes for different types of toys.”
Chidi got three boxes:
Now, Chidi could find any toy quickly. Each box was like a database – it stored similar things together. Inside each box, the toys were organised – for example, cars were arranged by colour.
Just like Chidi's toy boxes, computers store data in special containers. Some containers are like databases (organised, structured), some are like data lakes (a big pool of raw data), and some are like data warehouses (organised for analysis).
Let's explore these containers!
Definition: A database is a collection of data that is organised so that it can be easily accessed, managed, and updated.
Why is it important? Without databases, we would have to search through piles of data to find what we need.
Simple explanation: A database is like a giant, organised filing cabinet. Each drawer has files, and each file has papers with data.
Real‑life example: A school's student database stores the names, ages, and grades of all students.
School example: Your school uses a database to keep track of attendance.
Home example: Your phone's contact list is a small database.
Nigerian example: The NIN database stores information for millions of Nigerians.
Illustration:
+---------------------+
| Database |
+---------------------+
| Student Name | Age |
+---------------------+
| Ada | 10 |
| Chidi | 12 |
+---------------------+
Mini summary: A database is an organised collection of data that is easy to access and update.
Definition: A table is a way to organise data in rows and columns – like a spreadsheet.
Why is it important? Tables make it easy to see relationships between different pieces of data.
Simple explanation: Think of a table like a grid. Each row is a record (a single item), and each column is a field (a type of information).
Real‑life example: A teacher's gradebook – each row is a student, and each column is a subject.
School example: A timetable – rows are periods, columns are days of the week.
Home example: A chore chart – rows are chores, columns are days of the week.
Nigerian example: A market price list – rows are items, columns are prices from different sellers.
Illustration:
+---------------------+----------------+----------------+
| Name | Age | Class |
+---------------------+----------------+----------------+
| Ada | 10 | Primary 5 |
| Chidi | 12 | JSS 1 |
+---------------------+----------------+----------------+
Mini summary: A table organises data in rows and columns.
Definition: A relational database stores data in tables that are connected to each other through relationships.
Why is it important? It allows us to link data from different tables – like linking a student to their classes.
Simple explanation: Imagine you have two tables: one for students and one for classes. A relational database can link a student to the classes they are taking.
Real‑life example: A hospital database links patients to their doctors.
School example: A school database links students to their teachers.
Home example: A family database links parents to their children.
Nigerian example: A bank database links customers to their accounts.
Illustration:
+------------------+ +------------------+
| Students | | Classes |
+------------------+ +------------------+
| ID | Name | | ID | Subject |
+------------------+ +------------------+
| 1 | Ada | | 1 | Math |
| 2 | Chidi | | 2 | Science |
+------------------+ +------------------+
| |
+----------+-----------------+
|
v
+-------------------------------------+
| Student_Classes (links them) |
+-------------------------------------+
| Student_ID | Class_ID |
+-------------------------------------+
| 1 | 1 |
| 2 | 2 |
+-------------------------------------+
Mini summary: Relational databases connect tables using relationships.
Definition: SQL (Structured Query Language) is a special language used to talk to databases and get the data you need.
Why is it important? SQL is the most common way to interact with databases – it's like the language of data.
Simple explanation: SQL is like asking a librarian for a book – you say "I want all books by this author" and the librarian (database) brings them to you.
Real‑life example: When you search for a product on a website, the website uses SQL to find it in the database.
School example: A teacher uses SQL to find all students who scored above 80.
Home example: You use SQL to find all movies you watched last month.
Nigerian example: A bank uses SQL to find all transactions for a customer.
Illustration:
SQL Command:
SELECT * FROM Students WHERE Age > 10;
(This asks the database to give you all students older than 10.)
Mini summary: SQL is the language we use to ask databases for data.
Definition: NoSQL databases are databases that do not use the traditional table format – they can store data in documents, key‑value pairs, or graphs.
Why is it important? NoSQL databases are great for storing large amounts of unstructured data – like social media posts.
Simple explanation: While relational databases are like a filing cabinet, NoSQL databases are like a big box where you can throw different types of items.
Real‑life example: Facebook uses NoSQL databases to store posts, photos, and comments.
School example: A school might use NoSQL to store student portfolios with different types of files.
Home example: A smart home might use NoSQL to store data from different sensors.
Nigerian example: A fintech app might use NoSQL to store transaction data.
Illustration:
NoSQL Document:
{
"name": "Ada",
"age": 10,
"subjects": ["Math", "Science"],
"address": {"city": "Lagos", "state": "Lagos"}
}
Mini summary: NoSQL databases are flexible and can store many types of data.
Definition: A data lake is a large storage place where you can keep raw data in its original format – like a giant pool of data.
Why is it important? Data lakes let you store all your data without having to organise it first. You can decide how to use it later.
Simple explanation: Imagine a big lake where you can throw all your toys – cars, dolls, blocks – without sorting them. Later, you can dive in and pick out what you need.
Real‑life example: A company might store all its logs, customer data, and sensor data in a data lake.
School example: A school might store all student records, teacher notes, and photos in a data lake.
Home example: You might store all your family photos and videos in a data lake.
Nigerian example: The NIN system might use a data lake to store different types of citizen data.
Illustration:
+---------------------+
| Data Lake |
+---------------------+
| Raw Data |
| - Logs |
| - Images |
| - Documents |
| - Sensor data |
+---------------------+
Mini summary: A data lake stores raw data in its original form.
Definition: A data warehouse is a large storage place that holds organised, processed data that is ready for analysis and reporting.
Why is it important? Data warehouses make it easy to run reports and answer business questions.
Simple explanation: A data warehouse is like a library – the books are organised, catalogued, and ready to be read.
Real‑life example: A retail company uses a data warehouse to analyse sales trends.
School example: A school uses a data warehouse to analyse student performance over time.
Home example: You might use a data warehouse to track your spending habits.
Nigerian example: A bank uses a data warehouse to analyse customer transactions and detect fraud.
Illustration:
+---------------------+
| Data Warehouse |
+---------------------+
| Organised Data |
| - Sales reports |
| - Customer data |
| - Financial data |
+---------------------+
Mini summary: A data warehouse stores organised, processed data for analysis.
Definition: Data lakes store raw data; data warehouses store processed, organised data.
Why is it important? Choosing the right one depends on what you need to do with the data.
Simple explanation: A data lake is like a messy room where you throw everything. A data warehouse is like a tidy room where everything is in its place.
Real‑life example: A company uses a data lake to store all raw data, and a data warehouse to store cleaned, organised data for analysis.
School example: A school stores all student records in a data lake, and uses a data warehouse to generate report cards.
Home example: You store all family photos in a data lake, and use a data warehouse to create a photo album.
Nigerian example: A bank stores all transaction logs in a data lake, and uses a data warehouse to generate monthly statements.
Illustration:
+------------------+ +------------------+
| Data Lake | | Data Warehouse |
| (Raw Data) | | (Processed Data)|
+------------------+ +------------------+
| - Logs | -> | - Reports |
| - Images | | - Analytics |
| - Sensor data | | - Dashboards |
+------------------+ +------------------+
Mini summary: Data lakes store raw data; data warehouses store organised, processed data.
Definition: A lakehouse is a new type of storage that combines the best of data lakes and data warehouses – raw data storage with organised querying.
Why is it important? It gives you the flexibility of a data lake and the performance of a data warehouse.
Simple explanation: A lakehouse is like having a big room where you can throw everything, but also have shelves and labels to find things quickly.
Real‑life example: A modern company might use a lakehouse to store all their data and run fast analytics.
School example: A school might use a lakehouse to store student data and quickly generate reports.
Home example: You might use a lakehouse to store all your digital files and quickly search for anything.
Nigerian example: A fintech company might use a lakehouse to store transaction data and run real-time analytics.
Illustration:
+---------------------+
| Lakehouse |
+---------------------+
| Raw Data (like lake)|
| +----------------+ |
| | Organised (like | |
| | warehouse) | |
| +----------------+ |
+---------------------+
Mini summary: A lakehouse combines the features of data lakes and data warehouses.
Definition: Data in tables is organised into rows and columns. Rows are records (single items), and columns are fields (types of information).
Why is it important? This structure makes it easy to find, sort, and filter data.
Simple explanation: Rows are like people standing in a line; columns are like different pieces of information about each person.
Real‑life example: A spreadsheet with names in rows and scores in columns.
School example: A class register – rows are students, columns are attendance days.
Home example: A family budget – rows are expenses, columns are months.
Nigerian example: A market inventory – rows are items, columns are prices and quantities.
Illustration:
+----------+----------+----------+
| Name | Age | Grade | ← Columns
+----------+----------+----------+
| Ada | 10 | A | ← Row
| Chidi | 12 | B | ← Row
+----------+----------+----------+
Mini summary: Data is organised in rows (records) and columns (fields).
Definition: A primary key is a unique identifier for each row in a table. A foreign key is a link to a primary key in another table.
Why is it important? They help connect tables in a relational database.
Simple explanation: A primary key is like a student's ID number – it's unique for each student. A foreign key is like the class ID that links a student to their class.
Real‑life example: A hospital has patient IDs (primary keys) and doctor IDs (foreign keys).
School example: A student ID is a primary key, and the teacher ID in the class table is a foreign key.
Home example: A family tree – each person has a unique ID (primary key), and children link to parents (foreign keys).
Nigerian example: NIN is a primary key for citizens, and a bank account number can be a foreign key.
Illustration:
Students Table
+----------+----------+----------+
| ID (PK) | Name | Class_ID |
+----------+----------+----------+
| 1 | Ada | 101 |
| 2 | Chidi | 102 |
+----------+----------+----------+
Classes Table
+----------+----------+----------+
| ID (PK) | Class | Teacher |
+----------+----------+----------+
| 101 | Math | Mr. A |
| 102 | Science | Ms. B |
+----------+----------+----------+
Mini summary: Primary keys identify rows; foreign keys link tables.
Definition: A backup is a copy of data that can be used if the original data is lost or damaged.
Why is it important? Without backups, you could lose all your data – forever!
Simple explanation: A backup is like making a photocopy of your homework – if you lose the original, you still have a copy.
Real‑life example: Companies make daily backups of their data to protect against disasters.
School example: Your teacher makes copies of important documents.
Home example: You save your photos to the cloud as a backup.
Nigerian example: Banks make backups of customer data to prevent loss.
Illustration:
+------------------+ +------------------+
| Original Data | -- | Backup Copy |
+------------------+ +------------------+
| - Database | --> | - Database |
| - Files | | - Files |
+------------------+ +------------------+
Mini summary: Backups are copies of data to protect against loss.
Definition: Archiving means moving old data that is not used often to a special storage area for long-term keeping.
Why is it important? It keeps your main database fast and organised, while still keeping important old data.
Simple explanation: Archiving is like putting your old toys in a box in the attic – you don't need them every day, but you want to keep them.
Real‑life example: A bank archives old transaction data after 5 years.
School example: A school archives old student records after they graduate.
Home example: You archive old photos that you don't look at often.
Nigerian example: The NIN system archives old citizen records.
Illustration:
+------------------+ +------------------+
| Active Data | -- | Archived Data |
+------------------+ +------------------+
| - Recent sales | --> | - Old sales |
| - Current users | | - Old users |
+------------------+ +------------------+
Mini summary: Archiving is moving old data to long-term storage.
Definition: Cloud storage is a way to store data on remote servers that are accessible over the internet.
Why is it important? It allows you to access your data from anywhere and ensures it is safe and backed up.
Simple explanation: Cloud storage is like a giant, secure warehouse for your data, managed by a company like Google, Amazon, or Microsoft.
Real‑life example: Google Drive, iCloud, and OneDrive are all cloud storage services.
School example: A school stores assignments and projects in the cloud.
Home example: You store your photos in the cloud so you can see them on any device.
Nigerian example: Many Nigerian companies use cloud services like AWS and Azure.
Illustration:
Your Device → Internet → Cloud Storage
(Phone) → (Wi-Fi) → (Google Drive)
Mini summary: Cloud storage stores data on remote servers accessible via the internet.
Definition: A modern data architecture often uses a combination of databases, data lakes, and data warehouses.
Why is it important? Different types of data need different types of storage.
Simple explanation: You don't store all your things in one box – you use different boxes for different items. Similarly, data architects use different storage systems for different data.
Real‑life example: A company uses a database for daily transactions, a data lake for raw logs, and a data warehouse for reporting.
School example: A school uses a database for student records, a data lake for all documents, and a data warehouse for performance analysis.
Home example: You use a database for your contacts, a data lake for all your files, and a data warehouse for your budget analysis.
Nigerian example: A fintech uses a database for transactions, a data lake for all logs, and a data warehouse for business intelligence.
Illustration:
+-------------------------------------+
| Modern Data Architecture |
+-------------------------------------+
| +--------+ +--------+ +------+|
| | Database| |Data Lake| |DW ||
| |(OLTP) | |(Raw) | |(Analytics)|
| +--------+ +--------+ +------+|
+-------------------------------------+
Mini summary: A complete data architecture uses different storage systems for different needs.
| Word | Simple Definition |
|---|---|
| Database | An organised collection of data. |
| Table | Data organised in rows and columns. |
| Relational Database | A database with tables connected by relationships. |
| SQL | A language used to talk to databases. |
| NoSQL | A database that stores data without tables. |
| Data Lake | A storage place for raw data. |
| Data Warehouse | A storage place for processed, organised data. |
| Lakehouse | A combination of a data lake and a data warehouse. |
| Primary Key | A unique identifier for a row. |
| Foreign Key | A link to a primary key in another table. |
| Backup | A copy of data for protection. |
| Archive | Old data stored for long-term keeping. |
| Cloud Storage | Data stored on remote servers over the internet. |
This module introduces the key storage concepts in data architecture. Use plenty of visual aids – tables, diagrams, and comparisons. Encourage students to think about data storage in their daily lives – contacts, photos, documents. The goal is to build a solid understanding of databases, data lakes, and data warehouses.
Encourage your child to think about how data is stored in their daily lives – in phones, in the cloud, in notebooks. Discuss the difference between organised storage (warehouse) and raw storage (lake). Help them understand the importance of backups and archiving.
| Feature | Database | Data Lake | Data Warehouse |
|---|---|---|---|
| Data Type | Structured | Raw, unstructured | Processed, structured |
| Use Case | Transactions | Storage, exploration | Analytics, reporting |
| Example | MySQL | Amazon S3 | Snowflake |
+----------+----------+----------+----------+
| ID (PK) | Name | Age | Grade |
+----------+----------+----------+----------+
| 1 | Ada | 10 | A |
| 2 | Chidi | 12 | B |
| 3 | Kofi | 11 | A |
+----------+----------+----------+----------+
+------------------+ +------------------+
| Data Lake | | Data Warehouse |
| (Raw Data) | | (Organised Data)|
+------------------+ +------------------+
| - All data | -> | - Clean data |
| - No structure | | - Structured |
| - Cheap storage | | - Optimized |
+------------------+ +------------------+
You have completed Module 2 – "Storing Data"! You now know about databases, data lakes, and data warehouses. You understand how data is organised in tables and how SQL is used to communicate with databases. You also learned about backups and archiving.
These concepts are the foundation of data architecture. Data architects choose the right storage system based on the type of data and what it will be used for.
Great work – you are now ready for Module 3!
| Term | Definition |
|---|---|
| 1. Database | A. Stores raw data |
| 2. Data Lake | B. An organised collection of data |
| 3. Data Warehouse | C. A language to query databases |
| 4. SQL | D. Stores processed data |
| 5. Primary Key | E. A unique identifier for a row |
Answers: 1‑B, 2‑A, 3‑D, 4‑C, 5‑E
Scenario 1: A school wants to store student data. They need a system to track grades, attendance, and contact information. What type of storage would you recommend? Why?
Scenario 2: A company has large amounts of raw data from sensors. They want to store it and later analyse it. What type of storage would you recommend? Why?
In groups, design a data storage plan for a Nigerian business – e.g., a bank, a market, or a school. Decide what types of data they need to store, and choose the best storage systems (database, data lake, data warehouse) for each type. Present your plan to the class.
Think about a personal project – e.g., tracking your expenses or organising your photos. Design a data storage plan for your project. Include a database, a data lake, and a data warehouse if needed. Write down your plan and explain your choices.
Design a Database for a School: Create a database with tables for students, teachers, and classes. Define primary keys, foreign keys, and relationships. Write a simple SQL query to find all students in a specific class.
Create a data storage plan for a small business – e.g., a retail shop. Include a database for sales, a data lake for logs, and a data warehouse for analytics. Explain why you chose each system.
Design a complete data architecture for a Nigerian fintech company. Include databases for transactions, data lakes for logs, and data warehouses for analytics. Also include backup and archiving strategies. Present your design in detail.
Fill‑in‑the‑Blank: 1. database, 2. rows, 3. relational, 4. SQL, 5. data lake, 6. data warehouse, 7. lakehouse, 8. primary, 9. foreign, 10. backup.
True/False: 1F, 2T, 3F, 4T, 5F, 6F, 7F, 8T, 9T, 10T.
Multiple Choice: 1B, 2B, 3A, 4B, 5A, 6A, 7B, 8A, 9B, 10A, 11A, 12B, 13C, 14B, 15B.
In Module 3, you will learn about data modeling – how to design the structure of your data. You will learn about Entity-Relationship Diagrams (ERDs), normalization, and different types of schemas. To prepare, think about how you would organise data for a project – what tables would you need, and how would they be connected?
Excellent work, future Data Architect! See you in Module 3!
Hello, future Data Architect! In Module 2, you learned about databases, data lakes, and data warehouses. You know where data is stored. Now, it's time to learn how data is organised – this is called data modeling.
Think of a data model like a blueprint for a house. Before you build a house, you need a plan that shows where the rooms, doors, and windows go. A data model is the same – it shows how data is structured, connected, and organised.
In this module, you will learn about different types of data models, how to create them, and why they are so important. You will also learn about normalisation – a way to make your data clean and organised.
Let's start with a story!
After this module, you will be able to:
Kofi loved reading books. He had a huge collection at home, but they were all in a big pile. He could never find the book he wanted. He decided to organise his books.
First, he sorted them by genre – adventure, science, and fantasy. Then, he arranged them by author's last name. Finally, he labelled each book with a number.
His friend, a data architect, said: "Kofi, you just created a data model! You decided how to organise your books – that's exactly what a data model does for data."
Kofi realised that a data model is like a map – it shows where everything is and how it's connected. Now, he could find any book in seconds.
Let's learn how to create our own data models!
Definition: A data model is a visual representation that shows how data is organised, what the data looks like, and how different pieces of data are connected to each other.
Why is it important? A data model is like a blueprint – it helps everyone understand the data and how it fits together before building anything.
Simple explanation: A data model is like a map of a city. It shows the streets (data), the buildings (tables), and how they are connected (relationships).
Real‑life example: A library uses a data model to organise books by genre, author, and title.
School example: A school uses a data model to organise students, teachers, and classes.
Home example: You use a data model to organise your closet – shirts in one section, pants in another.
Nigerian example: A market uses a data model to organise items by category – fruits, vegetables, grains.
Illustration:
+---------------------+
| Data Model |
+---------------------+
| Tables: |
| - Students |
| - Teachers |
| - Classes |
+---------------------+
| Relationships: |
| - Students take |
| Classes |
| - Teachers teach |
| Classes |
+---------------------+
Mini summary: A data model is a blueprint that shows how data is organised and connected.
Definition: There are three levels of data models: conceptual (high-level), logical (more detailed), and physical (implementation-specific).
Why is it important? Different people need different levels of detail – business people need conceptual, developers need physical.
Simple explanation: Conceptual is like a map of a country; logical is like a map of a city; physical is like a map of a neighbourhood.
Real‑life example: A conceptual model shows "students take classes"; a logical model shows "Student(ID, Name) and Class(ID, Name)"; a physical model shows the actual SQL tables.
School example: Conceptual: "We have students"; Logical: "Students have IDs, names, and grades"; Physical: "CREATE TABLE students (id INT, name VARCHAR...)"
Home example: Conceptual: "We have rooms"; Logical: "Rooms have names and sizes"; Physical: "Tables for rooms with dimensions."
Nigerian example: Conceptual: "We have citizens"; Logical: "Citizens have NIN, name, address"; Physical: "SQL tables for NIN database."
Illustration:
+-------------------------------------+
| Conceptual (Business view) |
| - Students and classes |
+-------------------------------------+
|
v
+-------------------------------------+
| Logical (Detailed structure) |
| - Student(ID, Name, Age) |
| - Class(ID, Name, Teacher) |
+-------------------------------------+
|
v
+-------------------------------------+
| Physical (Database implementation) |
| - CREATE TABLE students (...) |
| - CREATE TABLE classes (...) |
+-------------------------------------+
Mini summary: Conceptual is high-level; logical is detailed; physical is the actual database implementation.
Definition: An entity is an object or thing you want to store data about (like a student). Attributes are the pieces of information about that entity (like name, age, and grade).
Why is it important? Entities and attributes are the building blocks of data models.
Simple explanation: An entity is like a person; attributes are like their name, age, and height.
Real‑life example: In a library, "Book" is an entity; "Title", "Author", and "Year" are attributes.
School example: "Student" is an entity; "Name", "Age", and "Grade" are attributes.
Home example: "Car" is an entity; "Make", "Model", and "Color" are attributes.
Nigerian example: "Citizen" is an entity; "NIN", "Name", and "Address" are attributes.
Illustration:
Entity: Student
Attributes:
- ID (primary key)
- Name
- Age
- Grade
Mini summary: Entities are objects; attributes are properties of those objects.
Definition: A relationship is how two or more entities are connected to each other.
Why is it important? Relationships show how data is linked – they are the connections in your data model.
Simple explanation: A relationship is like a friendship – two people are connected because they know each other.
Real‑life example: A student "takes" a class – that's a relationship between Student and Class.
School example: A teacher "teaches" a subject – that's a relationship.
Home example: A parent "has" a child – that's a relationship.
Nigerian example: A citizen "has" a NIN – that's a relationship.
Illustration:
+----------+ +----------+
| Student | takes | Class |
+----------+ +----------+
| ID |--------->| ID |
| Name | | Name |
+----------+ +----------+
Mini summary: Relationships show how entities are connected.
Definition: Relationships can be one-to-one (1:1), one-to-many (1:N), or many-to-many (M:N).
Why is it important? The type of relationship determines how you design your database tables.
Simple explanation: One-to-one: one person has one passport. One-to-many: one teacher has many students. Many-to-many: many students take many classes.
Real‑life example: A person has one birth certificate (1:1). A mother has many children (1:N). Students and classes (M:N).
School example: A student has one locker (1:1). A teacher teaches many classes (1:N). Students take many classes and classes have many students (M:N).
Home example: A house has one address (1:1). A family has many members (1:N). People and hobbies (M:N).
Nigerian example: A citizen has one NIN (1:1). A bank has many customers (1:N). Customers and accounts (M:N).
Illustration:
1:1 Person ---- has ---- Passport
1:N Teacher ---- teaches ---- Students
M:N Students ---- take ---- Classes
Mini summary: Relationships can be one-to-one, one-to-many, or many-to-many.
Definition: An ERD is a picture that shows entities, attributes, and relationships in a data model.
Why is it important? ERDs are the most common way to visualise data models – they are like maps for data.
Simple explanation: An ERD is like a drawing of your data model – it shows all the pieces and how they fit together.
Real‑life example: A company uses an ERD to design its customer database.
School example: A school uses an ERD to design its student information system.
Home example: You might draw an ERD to organise your family tree.
Nigerian example: The NIN system has an ERD to show how citizens, IDs, and addresses are related.
Illustration:
+----------+ +----------+ +----------+
| Student | | Class | | Teacher |
+----------+ +----------+ +----------+
| ID | | ID | | ID |
| Name | | Name | | Name |
| Age | | Teacher_ID| | |
+----------+ +----------+ +----------+
| | |
+---------+-----------+ |
| |
v |
+-----------------+ |
| Takes | |
+-----------------+ |
| Student_ID | |
| Class_ID | |
+-----------------+ |
| |
+-----------------------------------+
Mini summary: ERDs are visual diagrams that show entities, attributes, and relationships.
Definition: Normalisation is the process of organising data in a database to reduce redundancy (duplication) and improve integrity.
Why is it important? Normalisation makes your database cleaner, faster, and easier to maintain.
Simple explanation: Normalisation is like cleaning your room – you put things in the right place so you can find them easily.
Real‑life example: Instead of storing a customer's address in every order, you store it once in a customer table.
School example: Instead of storing a teacher's name in every class, you store it once in a teacher table.
Home example: Instead of writing your address on every bill, you keep it in one place.
Nigerian example: Instead of storing a citizen's address in multiple places, you keep it in one central record.
Illustration:
Before Normalisation (Redundant):
+----------+----------+----------+----------+
| Order_ID | Customer | Address | Product |
+----------+----------+----------+----------+
| 1 | Ada | Lagos | Apple |
| 2 | Ada | Lagos | Orange |
+----------+----------+----------+----------+
After Normalisation (Clean):
Customers Table:
+----------+----------+----------+
| ID | Name | Address |
+----------+----------+----------+
| 1 | Ada | Lagos |
+----------+----------+----------+
Orders Table:
+----------+----------+----------+
| Order_ID | Customer_ID| Product |
+----------+----------+----------+
| 1 | 1 | Apple |
| 2 | 1 | Orange |
+----------+----------+----------+
Mini summary: Normalisation removes redundancy and organises data cleanly.
Definition: 1NF requires that each cell has a single value and each column has unique values.
Why is it important? 1NF is the first step in normalisation – it ensures your data is atomic (single values).
Simple explanation: Each box should contain only one thing, not a list.
Real‑life example: Instead of storing "Apple, Banana" in one cell, store them in separate rows.
School example: Instead of storing "Math, Science" in one cell, store them in separate rows.
Home example: Instead of storing "red, blue" in one cell, store them in separate rows.
Nigerian example: Instead of storing multiple phone numbers in one cell, store them in separate rows.
Illustration:
Before 1NF:
+----------+----------+
| Student | Subjects |
+----------+----------+
| Ada | Math, Sci|
+----------+----------+
After 1NF:
+----------+----------+
| Student | Subject |
+----------+----------+
| Ada | Math |
| Ada | Science |
+----------+----------+
Mini summary: 1NF makes sure each cell has only one value.
Definition: 2NF removes partial dependencies – all data must depend on the whole primary key, not just part of it.
Why is it important? 2NF further reduces redundancy and improves data integrity.
Simple explanation: If you have a composite key (two fields), all other data must depend on both, not just one.
Real‑life example: If a table has keys "Student_ID" and "Subject_ID", the grade depends on both, but the subject name depends only on Subject_ID – so you split it.
School example: A table with Student_ID and Subject_ID – the subject name belongs in a separate subject table.
Home example: A table with Person_ID and Hobby_ID – the hobby name belongs in a separate hobby table.
Nigerian example: A table with Citizen_ID and State_ID – the state name belongs in a separate state table.
Illustration:
Before 2NF (Partial dependency):
+----------+----------+----------+
| Student_ID| Subject_ID| Subject |
+----------+----------+----------+
| 1 | 101 | Math |
| 1 | 102 | Science |
+----------+----------+----------+
(Subject depends on Subject_ID, not on Student_ID)
After 2NF:
+----------+----------+----------+
| Student_ID| Subject_ID| Grade |
+----------+----------+----------+
| 1 | 101 | A |
| 1 | 102 | B |
+----------+----------+----------+
Subjects Table:
+----------+----------+
| Subject_ID| Subject |
+----------+----------+
| 101 | Math |
| 102 | Science |
+----------+----------+
Mini summary: 2NF removes partial dependencies – all data depends on the whole key.
Definition: 3NF removes transitive dependencies – non-key fields should not depend on other non-key fields.
Why is it important? 3NF is the most common normalisation level – it ensures data is clean and well-organised.
Simple explanation: If A depends on B, and B depends on C, then A depends on C – that's a transitive dependency. 3NF removes it.
Real‑life example: If a table has "Student_ID", "Teacher_ID", and "Teacher_Name", the Teacher_Name depends on Teacher_ID, not on Student_ID.
School example: A table with Student_ID and Teacher_ID – the teacher name belongs in a separate teacher table.
Home example: A table with Person_ID and City_Name – the city name belongs in a separate city table.
Nigerian example: A table with Citizen_ID and LGA_Name – the LGA name belongs in a separate LGA table.
Illustration:
Before 3NF (Transitive dependency):
+----------+----------+----------+
| Student_ID| Teacher_ID| Teacher |
+----------+----------+----------+
| 1 | 101 | Mr. A |
| 2 | 102 | Ms. B |
+----------+----------+----------+
(Teacher depends on Teacher_ID, not Student_ID)
After 3NF:
+----------+----------+
| Student_ID| Teacher_ID|
+----------+----------+
| 1 | 101 |
| 2 | 102 |
+----------+----------+
Teachers Table:
+----------+----------+
| Teacher_ID| Teacher |
+----------+----------+
| 101 | Mr. A |
| 102 | Ms. B |
+----------+----------+
Mini summary: 3NF removes transitive dependencies – non-key fields depend only on the primary key.
Definition: Denormalisation is intentionally adding redundancy to improve performance.
Why is it important? Sometimes, normalisation makes queries slow – denormalisation can speed things up.
Simple explanation: Sometimes you need to break the rules to get better performance – like making extra copies of data for faster reading.
Real‑life example: A data warehouse often denormalises data to make reports run faster.
School example: Storing a student's name in the grade table to avoid joining tables.
Home example: Keeping a list of family members in a quick-access list.
Nigerian example: A bank might denormalise transaction data for faster reporting.
Illustration:
Normalised: Students (ID, Name) | Grades (Student_ID, Grade)
Denormalised: Grades (Student_ID, Student_Name, Grade)
Mini summary: Denormalisation adds redundancy for performance but should be used carefully.
Definition: A star schema is a data warehouse model with one large "fact" table and many smaller "dimension" tables.
Why is it important? Star schemas are simple and fast for analytics and reporting.
Simple explanation: The fact table is in the centre (like the sun), and dimension tables are around it (like planets).
Real‑life example: A sales data warehouse – the fact table has sales, and dimensions are time, product, and store.
School example: A school data warehouse – the fact table has grades, and dimensions are student, class, and semester.
Home example: A budget data warehouse – the fact table has expenses, and dimensions are category, month, and payment method.
Nigerian example: A bank data warehouse – the fact table has transactions, and dimensions are customer, account, and date.
Illustration:
+------------------+
| Time |
+------------------+
|
v
+------------------+ +------------------+
| Product |--------->| Fact Table |
+------------------+ +------------------+
| | Sales |
+------------------->| Product_ID |
| Time_ID |
| Store_ID |
+------------------+ +------------------+
| Store |<----------+
+------------------+
Mini summary: A star schema has a central fact table surrounded by dimension tables.
Definition: A snowflake schema is a star schema where dimension tables are further normalised into sub-dimensions.
Why is it important? Snowflake schemas save storage space but can be slower for queries.
Simple explanation: A snowflake is like a star schema where some dimensions are split into smaller pieces.
Real‑life example: A product dimension might be split into product, brand, and category.
School example: A student dimension might be split into student, class, and teacher.
Home example: A grocery dimension might be split into item, category, and supplier.
Nigerian example: A customer dimension might be split into customer, region, and city.
Illustration:
+------------------+
| Time |
+------------------+
|
v
+------------------+ +------------------+
| Product |--------->| Fact Table |
+------------------+ +------------------+
| | Sales |
v | Product_ID |
+------------------+ | Time_ID |
| Brand | +------------------+
+------------------+
|
v
+------------------+
| Category |
+------------------+
Mini summary: A snowflake schema is a star schema with normalised dimensions.
Definition: Best practices are guidelines for creating high-quality data models.
Why is it important? Following best practices ensures your data model is clean, efficient, and easy to use.
Simple explanation: Best practices are like house rules – they help everyone do the right thing.
Real‑life example: Use descriptive names for entities and attributes.
School example: Use "Student" instead of "S" for a table name.
Home example: Use "Room" instead of "R" for a room list.
Nigerian example: Use "Citizen" instead of "C" for citizen data.
Illustration:
Best Practices:
- Use clear, descriptive names
- Define primary keys for every table
- Use foreign keys to link tables
- Normalise data to reduce redundancy
- Document your data model
Mini summary: Best practices help you create clean, efficient, and understandable data models.
Definition: A complete data model combines all the concepts – entities, attributes, relationships, normalisation, and schemas.
Why is it important? This is what data architects do every day – design data models for real-world problems.
Simple explanation: You use all the tools you've learned to build a complete blueprint for your data.
Real‑life example: A data architect designs a data model for a company's customer management system.
School example: A school data model includes students, teachers, classes, grades, and attendance.
Home example: A family data model includes people, relationships, events, and belongings.
Nigerian example: A NIN data model includes citizens, addresses, and identification documents.
Illustration:
+-------------------------------------------+
| Complete Data Model |
+-------------------------------------------+
| Entities: Students, Teachers, Classes |
| Attributes: Names, IDs, Grades |
| Relationships: Takes, Teaches |
| Normalisation: 3NF |
| Schema: Star or Snowflake |
+-------------------------------------------+
Mini summary: A complete data model uses all the concepts you've learned to design a clean, efficient data structure.
| Word | Simple Definition |
|---|---|
| Data Model | A blueprint that shows how data is organised. |
| Entity | An object or thing you store data about. |
| Attribute | A piece of information about an entity. |
| Relationship | How two entities are connected. |
| ERD | Entity-Relationship Diagram – a visual data model. |
| Normalisation | Organising data to reduce redundancy. |
| 1NF | First Normal Form – each cell has a single value. |
| 2NF | Second Normal Form – no partial dependencies. |
| 3NF | Third Normal Form – no transitive dependencies. |
| Denormalisation | Adding redundancy for performance. |
| Star Schema | A data warehouse model with a central fact table. |
| Snowflake Schema | A star schema with normalised dimensions. |
| Primary Key | A unique identifier for a row. |
| Foreign Key | A link to a primary key in another table. |
This module introduces data modeling – the heart of data architecture. Use lots of visual aids – ERDs, tables, and comparisons. Encourage students to practice by drawing ERDs for everyday scenarios. Normalisation can be tricky – use simple examples to explain each normal form. The goal is for students to feel comfortable creating and understanding data models.
Encourage your child to think about data models in their daily lives – how is their school data organised? How about their game inventory? Help them draw simple ERDs on paper. Normalisation can be explained as "cleaning up" data – putting things in the right place.
+----------+ +----------+
| Student | | Class |
+----------+ +----------+
| ID | | ID |
| Name |<-------->| Name |
| Age | | Teacher |
+----------+ +----------+
| Normal Form | Requirement | Example |
|---|---|---|
| 1NF | Single-valued cells | No lists in cells |
| 2NF | No partial dependencies | All data depends on whole key |
| 3NF | No transitive dependencies | No data depends on other non-key data |
+------------------+
| Time |
+------------------+
|
v
+------------------+ +------------------+
| Product |--------->| Fact Table |
+------------------+ +------------------+
| | Sales |
+------------------->| Product_ID |
| Time_ID |
| Store_ID |
+------------------+ +------------------+
| Store |<----------+
+------------------+
You have completed Module 3 – "Data Modeling"! You now know how to design the structure of data using entities, attributes, and relationships. You can create ERDs, normalise data, and understand star and snowflake schemas.
Data modeling is one of the most important skills for a data architect – it's how you turn real-world problems into organised data structures.
Excellent work – you are now ready for Module 4!
| Term | Definition |
|---|---|
| 1. Entity | A. A piece of information about an entity |
| 2. Attribute | B. An object you store data about |
| 3. Relationship | C. A blueprint for data organisation |
| 4. Data Model | D. How entities are connected |
| 5. Normalisation | E. Organising data to reduce redundancy |
Answers: 1‑B, 2‑A, 3‑D, 4‑C, 5‑E
Scenario 1: A school wants to design a database for students, teachers, and classes. Create a data model with entities, attributes, and relationships. Draw an ERD.
Scenario 2: A hospital wants to store patient data, doctor data, and appointments. Normalise the data and create a star schema for reporting.
In groups, design a data model for a Nigerian business – e.g., a bank, a market, or a school. Create an ERD, identify entities, attributes, and relationships. Normalise the data to 3NF. Present your model to the class.
Design a data model for a personal project – e.g., a movie collection, a recipe book, or a contact list. Create an ERD, normalise the data, and explain your design choices.
Design a Data Model for a Library: Create a data model for a library with books, authors, members, and loans. Identify entities, attributes, and relationships. Draw an ERD and normalise the data to 3NF.
Design a data model for a retail store – customers, orders, products, and categories. Create an ERD, normalise to 3NF, and implement the model as SQL tables.
Design a star schema for a sales data warehouse. Include fact and dimension tables. Explain why you chose each dimension and how the fact table is structured.
Fill‑in‑the‑Blank: 1. data model, 2. entity, 3. attribute, 4. relationship, 5. Normalisation, 6. single, 7. partial, 8. transitive, 9. star, 10. Denormalisation.
True/False: 1F, 2F, 3T, 4T, 5T, 6F, 7F, 8T, 9T, 10F.
Multiple Choice: 1B, 2B, 3B, 4B, 5A, 6B, 7C, 8A, 9B, 10A, 11A, 12B, 13B, 14B, 15D.
In Module 4, you will learn about data integration and ETL – how to move and transform data from one system to another. You will learn about batch and streaming data, and how to build data pipelines. To prepare, think about how data moves from your phone to the cloud, and from the cloud to your computer.
Amazing work, future Data Architect! See you in Module 4!
Hello, future Data Architect! In Module 3, you learned how to design data models – the blueprint for your data. Now, we are going to learn how to move data from one place to another. This is called data integration.
Think of data like water. Water comes from many sources – rain, rivers, and taps. To use it, we need to collect it, clean it, and send it where it's needed. Data is the same – it comes from many sources, needs to be cleaned, and then sent to storage or analysis systems.
In this module, you will learn about ETL (Extract, Transform, Load) and ELT (Extract, Load, Transform). You will also learn about batch and streaming data, and how to build data pipelines.
Let's start with a story!
After this module, you will be able to:
Ngozi ran a small orange juice factory. She bought oranges from many different farmers. Each farmer delivered oranges in different boxes – some big, some small, some with labels, some without.
Ngozi had to extract the oranges from the boxes, transform them by washing and peeling, and load them into the juicing machine.
Her friend, a data architect, said: "Ngozi, you are doing ETL! You extract from the farmers, transform by washing and peeling, and load into the juicer. Data works the same way."
Ngozi understood. Data integration is like making orange juice – you collect data from different sources, clean it, and put it where it can be used.
Now, let's learn how to do this with data!
Definition: Data integration is the process of combining data from different sources into a unified view.
Why is it important? Most organizations have data scattered across many systems – integration brings it all together.
Simple explanation: Data integration is like making a salad – you take different ingredients (data), mix them together, and create a single dish (unified data).
Real‑life example: A company combines sales data, customer data, and inventory data to get a complete view of their business.
School example: A school combines attendance data, grade data, and demographic data to understand student performance.
Home example: You combine your calendar, to-do list, and contacts to plan your day.
Nigerian example: A bank combines transaction data, customer data, and branch data for reporting.
Illustration:
+----------+ +----------+
| Source 1 | | Source 2 |
+----------+ +----------+
| |
+---------+-----------+
|
v
+-------------+
| Integrated |
| Data |
+-------------+
Mini summary: Data integration combines data from different sources into a unified view.
Definition: ETL stands for Extract, Transform, Load – a process where data is extracted from sources, transformed (cleaned and changed), and loaded into a target system.
Why is it important? ETL is the most common way to move and prepare data for analysis.
Simple explanation: ETL is like cooking – you take ingredients (extract), prepare them (transform), and serve the dish (load).
Real‑life example: A company extracts sales data from multiple stores, transforms it by calculating totals, and loads it into a data warehouse.
School example: A school extracts grades from different subjects, transforms them into a report card, and loads them into the student database.
Home example: You extract money from your wallet, transform it into a list of expenses, and load it into your budget spreadsheet.
Nigerian example: A fintech extracts transaction data, transforms it to detect fraud, and loads it into a reporting system.
Illustration:
+----------+ +----------+ +----------+
| Extract | -------> | Transform| -------> | Load |
+----------+ +----------+ +----------+
| Get data | | Clean | | Store in |
| from | | Validate | | Database |
| sources | | Map | | |
+----------+ +----------+ +----------+
Mini summary: ETL is Extract, Transform, Load – a three-step process for moving data.
Definition: ELT stands for Extract, Load, Transform – a process where data is extracted, loaded directly into the target system, and then transformed.
Why is it important? ELT is often faster and more flexible than ETL, especially with modern cloud systems.
Simple explanation: ELT is like putting all your groceries in the kitchen first (load), and then deciding what to cook (transform).
Real‑life example: A company extracts raw data, loads it into a cloud data warehouse, and then transforms it using SQL queries.
School example: A school extracts all student data, loads it into a database, and then transforms it for reporting.
Home example: You take all your photos, load them into a folder, and then sort them by date.
Nigerian example: A bank extracts transaction data, loads it into a data lake, and then transforms it for analytics.
Illustration:
+----------+ +----------+ +----------+
| Extract | -------> | Load | -------> | Transform|
+----------+ +----------+ +----------+
| Get data | | Load raw | | Clean |
| from | | into | | and |
| sources | | target | | Process |
+----------+ +----------+ +----------+
Mini summary: ELT is Extract, Load, Transform – load first, then transform.
Definition: In ETL, transformation happens before loading. In ELT, loading happens before transformation.
Why is it important? Choosing the right approach depends on your data, your tools, and your goals.
Simple explanation: ETL is like preparing ingredients before cooking; ELT is like cooking first and then deciding how to plate.
Real‑life example: ETL is used when you need clean data before loading; ELT is used when you have powerful systems that can transform data later.
School example: ETL: clean grades before storing. ELT: store grades and then calculate averages.
Home example: ETL: wash clothes before putting in closet. ELT: put clothes in closet and then sort.
Nigerian example: ETL: clean transaction data before loading to warehouse. ELT: load raw transactions and transform later.
Illustration:
ETL: Extract → Transform → Load
ELT: Extract → Load → Transform
Mini summary: ETL transforms before loading; ELT loads before transforming.
Definition: Batch data is data that is collected and processed in large groups (batches) at scheduled times.
Why is it important? Batch processing is simple, reliable, and good for large volumes of data.
Simple explanation: Batch data is like doing all your homework at once – you wait until the end of the day and do everything in one session.
Real‑life example: A company processes all sales data at midnight every day.
School example: A school processes grades at the end of each term.
Home example: You pay all your bills once a month.
Nigerian example: A bank processes all ATM transactions at the end of the day.
Illustration:
+----------+ +----------+ +----------+
| Collect | -------> | Wait | -------> | Process |
| Data | | | | All |
| over time| | | | Together |
+----------+ +----------+ +----------+
Mini summary: Batch data is processed in groups at scheduled times.
Definition: Streaming data is data that is processed continuously as it arrives.
Why is it important? Streaming is used for real-time applications – like live traffic updates or fraud detection.
Simple explanation: Streaming data is like drinking water from a fountain – it keeps coming and you take it as it arrives.
Real‑life example: A stock market app shows prices in real-time.
School example: A live quiz where scores are updated instantly.
Home example: A smart thermostat updates the temperature continuously.
Nigerian example: A fintech app detects fraud in real-time.
Illustration:
+----------+ +----------+ +----------+
| Data | -------> | Process | -------> | Action |
| Arrives | | instantly| | in |
| Continu- | | | | real-time|
| ously | | | | |
+----------+ +----------+ +----------+
Mini summary: Streaming data is processed in real-time as it arrives.
Definition: Batch processes large volumes of data at intervals; streaming processes data continuously.
Why is it important? Choosing between batch and streaming depends on latency requirements and data volume.
Simple explanation: Batch is like a bus – it picks up many passengers at once; streaming is like a taxi – it comes when you call.
Real‑life example: Batch is used for daily reports; streaming is used for live dashboards.
School example: Batch is for term reports; streaming is for live quiz scores.
Home example: Batch is for monthly budget; streaming is for live weather updates.
Nigerian example: Batch is for daily bank statements; streaming is for real-time fraud alerts.
Illustration:
Batch: Collect → Wait → Process → Store
Streaming: Collect → Process → Act → Collect → Process → Act
Mini summary: Batch processes data in intervals; streaming processes data continuously.
Definition: A data pipeline is a series of steps that move and process data from source to destination.
Why is it important? Pipelines are the backbone of data integration – they automate the flow of data.
Simple explanation: A data pipeline is like a conveyor belt – data moves from one station to the next, being processed along the way.
Real‑life example: A pipeline that moves sales data from online stores to a data warehouse.
School example: A pipeline that moves grades from teachers to the student database.
Home example: A pipeline that moves photos from your phone to the cloud.
Nigerian example: A pipeline that moves transaction data from branches to a central system.
Illustration:
+----------+ +----------+ +----------+
| Source | -------> | Process | -------> | Target |
+----------+ +----------+ +----------+
| Raw Data | | Clean | | Stored |
| | | Validate | | Data |
+----------+ +----------+ +----------+
Mini summary: A data pipeline moves and processes data from source to destination.
Definition: Data pipelines have stages: ingestion, processing, storage, and consumption.
Why is it important? Understanding the components helps you design and build effective pipelines.
Simple explanation: A pipeline is like a factory – raw materials come in, go through machines, and become finished products.
Real‑life example: Ingestion: collect data; Processing: clean and transform; Storage: save to database; Consumption: use for reports.
School example: Ingestion: collect grades; Processing: calculate averages; Storage: save to database; Consumption: print report cards.
Home example: Ingestion: take photos; Processing: organise; Storage: save to cloud; Consumption: view on phone.
Nigerian example: Ingestion: collect transactions; Processing: fraud detection; Storage: save to data warehouse; Consumption: dashboards.
Illustration:
+----------+ +----------+ +----------+ +----------+
| Ingestion| -> | Process | -> | Storage | -> | Consume |
+----------+ +----------+ +----------+ +----------+
| Collect | | Clean | | Database | | Report |
| Data | | Transform| | Data Lake| | Dashboard|
+----------+ +----------+ +----------+ +----------+
Mini summary: Data pipelines have stages: ingestion, processing, storage, and consumption.
Definition: Data quality is ensuring data is accurate, complete, consistent, and reliable during integration.
Why is it important? Bad data leads to bad decisions – data quality is critical in integration.
Simple explanation: Data quality is like checking ingredients before cooking – you want to make sure everything is fresh and correct.
Real‑life example: A company validates that all customer emails are correctly formatted.
School example: A school checks that student IDs are unique.
Home example: You check that your shopping list has the correct quantities.
Nigerian example: A bank validates that transaction amounts are positive.
Illustration:
Data Quality Checks:
- Accuracy: Is the data correct?
- Completeness: Is all data present?
- Consistency: Is the data consistent?
- Timeliness: Is the data up-to-date?
Mini summary: Data quality ensures data is accurate, complete, and consistent during integration.
Definition: Data validation is the process of checking that data meets certain rules or standards.
Why is it important? Validation catches errors before they cause problems.
Simple explanation: Data validation is like a security guard – it checks that everything is correct before it enters the building.
Real‑life example: A website checks that your email address has an "@" symbol.
School example: A school checks that grades are between 0 and 100.
Home example: You check that you have enough money before buying something.
Nigerian example: A bank checks that account numbers are 10 digits long.
Illustration:
Validation Rules:
- Not null: Data must exist
- Data type: Must be number, text, etc.
- Range: Must be within a range
- Format: Must match a pattern
Mini summary: Data validation checks that data meets specific rules or standards.
Definition: Data transformation is the process of converting data from one format or structure to another.
Why is it important? Data from different sources often comes in different formats – transformation makes it consistent.
Simple explanation: Data transformation is like translating a book from one language to another – you keep the meaning but change the words.
Real‑life example: Converting date formats from MM/DD/YYYY to DD/MM/YYYY.
School example: Converting a letter grade to a numeric grade.
Home example: Converting pounds to kilograms.
Nigerian example: Converting transaction amounts from naira to dollars.
Illustration:
Before Transformation: "01/15/2025"
After Transformation: "2025-01-15"
Mini summary: Data transformation converts data from one format to another.
Definition: There are many tools that help with data integration – Apache Kafka, Apache Spark, Informatica, and cloud services like AWS Glue.
Why is it important? Tools make the integration process faster, easier, and more reliable.
Simple explanation: Tools are like kitchen appliances – they help you cook faster and better.
Real‑life example: A company uses Apache Kafka for real-time streaming.
School example: A school uses a tool to integrate data from different systems.
Home example: You use Google Drive to integrate your files from different devices.
Nigerian example: A fintech uses Apache Spark for big data processing.
Illustration:
Data Integration Tools:
- Apache Kafka (streaming)
- Apache Spark (processing)
- Informatica (ETL)
- AWS Glue (cloud ETL)
- Talend (open source ETL)
Mini summary: Data integration tools help you process and move data efficiently.
Definition: Data lineage is the tracking of data as it moves from source to destination, including all transformations.
Why is it important? Lineage helps you understand where data comes from and how it has changed – crucial for debugging and compliance.
Simple explanation: Data lineage is like a map that shows the journey of data – from the source, through various steps, to the final destination.
Real‑life example: A company tracks how customer data moves from the website to the data warehouse.
School example: A school tracks how grades move from the teacher to the report card.
Home example: You track how your photos move from your phone to the cloud.
Nigerian example: A bank tracks how transaction data moves from branches to the central system.
Illustration:
Source → Extract → Transform → Load → Dashboard
(Website) → (API) → (Clean) → (Database) → (Report)
Mini summary: Data lineage tracks the flow of data from source to destination.
Definition: A complete data integration flow combines extraction, transformation, loading, and quality checks.
Why is it important? This is what real-world data integration looks like – it's a complete, end-to-end process.
Simple explanation: It's like a factory assembly line – raw materials go in, get processed, and come out as finished products.
Real‑life example: A company's complete integration flow: extract from sources, clean and transform, load to warehouse, validate data, and generate reports.
School example: Complete flow: collect grades, calculate averages, store in database, validate, and generate report cards.
Home example: Complete flow: take photos, organise, store in cloud, validate, and create albums.
Nigerian example: Complete flow: collect transactions, detect fraud, load to warehouse, validate, and generate dashboards.
Illustration:
+---------+ +---------+ +---------+ +---------+
| Extract | → | Clean | → | Load | → | Validate|
+---------+ +---------+ +---------+ +---------+
|
v
+---------+
| Report |
+---------+
Mini summary: A complete integration flow includes extraction, transformation, loading, validation, and reporting.
| Word | Simple Definition |
|---|---|
| Data Integration | Combining data from different sources. |
| ETL | Extract, Transform, Load – a process for moving data. |
| ELT | Extract, Load, Transform – another process for moving data. |
| Batch Data | Data processed in groups at scheduled times. |
| Streaming Data | Data processed in real-time as it arrives. |
| Data Pipeline | A series of steps that move and process data. |
| Data Quality | Ensuring data is accurate and complete. |
| Data Validation | Checking that data meets rules or standards. |
| Data Transformation | Converting data from one format to another. |
| Data Lineage | Tracking the flow of data from source to destination. |
This module introduces data integration and ETL – the process of moving data. Use real-world analogies (cooking, factories) to explain the concepts. Encourage students to think about how data moves in their daily lives. The goal is to build a strong understanding of how data is collected, processed, and delivered.
Encourage your child to think about how data moves from place to place – photos from phone to cloud, school grades from teacher to report card. Discuss the difference between batch (once a day) and streaming (all the time). Help them understand the importance of data quality and validation.
| Feature | ETL | ELT |
|---|---|---|
| Order | Extract → Transform → Load | Extract → Load → Transform |
| When to use | When you need clean data before loading | When you have powerful systems |
| Example | Traditional data warehouses | Cloud data warehouses |
| Feature | Batch | Streaming |
|---|---|---|
| Processing | In intervals | Continuous |
| Latency | High (minutes to hours) | Low (milliseconds to seconds) |
| Use case | Daily reports | Real-time dashboards |
+----------+ +----------+ +----------+ +----------+
| Sources | → | Extract | → | Transform| → | Load |
+----------+ +----------+ +----------+ +----------+
| DB, API, | | Get data | | Clean | | To Data |
| Files | | | | Map | | Warehouse|
+----------+ +----------+ +----------+ +----------+
|
v
+----------+
| Validate |
+----------+
|
v
+----------+
| Report |
+----------+
You have completed Module 4 – "Data Integration & ETL"! You now know how to move data from one place to another. You understand the difference between ETL and ELT, batch and streaming data, and the components of data pipelines.
Data integration is a critical skill for any data architect – it's how data moves from sources to storage and analytics. You now have the foundational knowledge to design and build data integration flows.
Great work – you are now ready for Module 5!
| Term | Definition |
|---|---|
| 1. ETL | A. Extract, Load, Transform |
| 2. ELT | B. Extract, Transform, Load |
| 3. Batch | C. Data processed in real-time |
| 4. Streaming | D. Data processed in groups |
| 5. Data Pipeline | E. A series of steps that move and process data |
Answers: 1‑B, 2‑A, 3‑D, 4‑C, 5‑E
Scenario 1: A retail company wants to integrate sales data from multiple stores. They need to generate daily reports. What integration approach would you recommend? Why?
Scenario 2: A fintech company needs to detect fraud in real-time. What approach would you recommend? Why?
In groups, design a data integration plan for a Nigerian business – e.g., a bank, a market, or a school. Decide on the approach (ETL or ELT), identify data sources, define transformations, and design the pipeline. Present your plan to the class.
Write a short essay explaining how data integration is used in a real-world application – e.g., a banking app, a weather app, or an e-commerce site. Include ETL/ELT, batch/streaming, and data quality considerations.
Design a Data Integration Flow: Choose a scenario (e.g., school grades, retail sales, bank transactions). Design a complete integration flow with sources, ETL/ELT process, transformations, validation, and target storage. Draw a diagram and write a description.
Write a detailed plan for integrating data from three different sources (e.g., a CSV file, a database, and an API). Include extraction, transformation (cleaning, mapping), loading, and validation steps.
Design a real-time data pipeline for a ride-sharing app. Include ingestion of location data, transformation (calculating distances, fares), and loading to a dashboard. Consider batch vs streaming, ETL vs ELT, and data quality checks.
Fill‑in‑the‑Blank: 1. Data integration, 2. Extract, 3. Transform, 4. Batch, 5. Streaming, 6. data pipeline, 7. Data quality, 8. Data validation, 9. Data transformation, 10. Data lineage.
True/False: 1T, 2F, 3F, 4F, 5T, 6F, 7T, 8T, 9T, 10F.
Multiple Choice: 1A, 2B, 3B, 4A, 5A, 6A, 7A, 8A, 9A, 10B, 11A, 12A, 13B, 14A, 15A.
In Module 5, you will learn about data governance and security – how to manage, protect, and ensure the quality of data. You will learn about compliance, privacy, and data protection. To prepare, think about how data is protected in your daily life – passwords, privacy settings, and secure websites.
Excellent work, future Data Architect! See you in Module 5!
Hello, future Data Architect! In Module 4, you learned how to move data from one place to another. Now, we are going to learn how to protect and manage data – this is called data governance and data security.
Think about your home. You have rules about who can enter, where things go, and how to keep things safe. Data governance is like the rules for data – who can access it, how it is used, and how it is protected. Data security is like locks on your doors – it keeps bad people out.
In this module, you will learn about data governance frameworks, security best practices, compliance with laws, and how to keep data private and safe.
Let's start with a story!
After this module, you will be able to:
Ade’s family had a big house with many rooms. Each room had different things – some rooms had valuables, some had documents, and some had everyday items.
To keep things safe, the family made rules:
Ade’s father, a data architect, said: “This is exactly what data governance and security are about. We have rules (governance) about who can access data, how it is protected (security), and we keep track of everything (compliance).”
Now, let's learn how to apply these rules to data!
Definition: Data governance is the set of rules, policies, and processes that ensure data is managed properly – who can access it, how it is used, and how it is protected.
Why is it important? Good governance ensures data is accurate, secure, and used responsibly.
Simple explanation: Data governance is like the rules of a game – they tell you how to play fairly and safely.
Real‑life example: A company has a policy that only certain employees can see customer data.
School example: A school has rules about who can see student grades.
Home example: Your family has rules about who can use which devices.
Nigerian example: A bank has policies about who can access customer accounts.
Illustration:
+---------------------+
| Data Governance |
+---------------------+
| - Rules |
| - Policies |
| - Roles |
| - Compliance |
+---------------------+
Mini summary: Data governance is the set of rules and policies for managing data properly.
Definition: Data governance includes data quality, data stewardship, data security, data privacy, and compliance.
Why is it important? All these components work together to ensure data is managed well.
Simple explanation: Data governance is like a team – each player has a role, and they work together to win.
Real‑life example: A company has a data governance team that manages policies, checks data quality, and ensures compliance.
School example: A school has policies for student data, checks for accuracy, and follows privacy laws.
Home example: Your family has rules for chores, checks that they are done, and follows safety guidelines.
Nigerian example: A bank has policies for customer data, checks data quality, and follows NDPR.
Illustration:
+---------------------------------------+
| Data Governance |
+---------------------------------------+
| +--------+ +--------+ +--------+ |
| | Quality| | Steward| |Security| |
| +--------+ +--------+ +--------+ |
| +--------+ +--------+ |
| |Privacy | |Compliance| |
| +--------+ +--------+ |
+---------------------------------------+
Mini summary: Data governance includes quality, stewardship, security, privacy, and compliance.
Definition: A data steward is a person who is responsible for managing and protecting data – they ensure data is accurate, secure, and used properly.
Why is it important? Data stewards are like guardians of data – they make sure data is treated well.
Simple explanation: A data steward is like a librarian – they organise books (data), make sure they are in good condition (quality), and ensure only authorised people borrow them (security).
Real‑life example: A company appoints a data steward to manage customer data.
School example: A teacher is a data steward for student grades.
Home example: A parent is a data steward for family information.
Nigerian example: A bank has data stewards for customer accounts.
Illustration:
+---------------------+
| Data Steward |
+---------------------+
| - Manages data |
| - Ensures quality |
| - Protects data |
| - Follows rules |
+---------------------+
Mini summary: A data steward is responsible for managing and protecting data.
Definition: Data security is the practice of protecting data from unauthorised access, theft, or damage.
Why is it important? If data is stolen or lost, it can cause serious problems – for individuals and organisations.
Simple explanation: Data security is like locking your doors and windows – you want to keep bad people out.
Real‑life example: A bank uses encryption to protect your money data.
School example: A school uses passwords to protect student records.
Home example: You lock your phone with a PIN to keep your photos private.
Nigerian example: A fintech uses encryption and secure servers to protect transaction data.
Illustration:
+---------------------+
| Data Security |
+---------------------+
| - Encryption |
| - Passwords |
| - Access control |
| - Backups |
| - Firewalls |
+---------------------+
Mini summary: Data security protects data from unauthorised access and theft.
Definition: Encryption is the process of scrambling data so that only authorised people can read it.
Why is it important? Even if someone steals encrypted data, they cannot read it without the key.
Simple explanation: Encryption is like writing a secret code – only people with the code book can read it.
Real‑life example: When you use a website, your data is often encrypted.
School example: A school encrypts student records to protect privacy.
Home example: You use a password manager that encrypts your passwords.
Nigerian example: A bank encrypts customer transaction data.
Illustration:
Plain Text: "Hello"
Encryption: "Xr%#k2"
Decryption: "Hello"
Mini summary: Encryption scrambles data so only authorised people can read it.
Definition: Access control is the practice of limiting who can access data and what they can do with it.
Why is it important? Not everyone needs access to all data – access control ensures people see only what they need.
Simple explanation: Access control is like having different keys – some keys open all doors, some open only certain rooms.
Real‑life example: In a company, managers can see all employee data, but regular employees can only see their own.
School example: Teachers can see student grades, but students can only see their own.
Home example: Parents have access to all devices, children have limited access.
Nigerian example: A bank has different access levels for different employees.
Illustration:
+---------------------+
| Access Control |
+---------------------+
| - Roles |
| - Permissions |
| - User groups |
+---------------------+
Mini summary: Access control limits who can see and use data.
Definition: Data privacy is the practice of protecting personal information – like names, addresses, and phone numbers – from misuse.
Why is it important? People have a right to keep their personal information private.
Simple explanation: Data privacy is like keeping your diary private – you don't want everyone to read it.
Real‑life example: A website asks for your permission before collecting your data.
School example: A school keeps student records confidential.
Home example: You keep your personal documents in a safe place.
Nigerian example: A bank keeps customer information private and secure.
Illustration:
+---------------------+
| Data Privacy |
+---------------------+
| - Personal data |
| - Consent |
| - Confidentiality |
+---------------------+
Mini summary: Data privacy protects personal information from misuse.
Definition: Compliance means following laws, regulations, and policies related to data.
Why is it important? Non-compliance can lead to fines and loss of trust.
Simple explanation: Compliance is like following traffic rules – you do it to stay safe and avoid penalties.
Real‑life example: A company follows GDPR (a data protection law) to protect customer data.
School example: A school follows laws about student data privacy.
Home example: You follow rules about sharing personal information online.
Nigerian example: A bank follows NDPR (Nigeria Data Protection Regulation).
Illustration:
+---------------------+
| Compliance |
+---------------------+
| - Laws |
| - Regulations |
| - Policies |
+---------------------+
Mini summary: Compliance means following laws and regulations about data.
Definition: GDPR (General Data Protection Regulation) is a law in Europe that protects people's data and gives them control over it.
Why is it important? It sets a high standard for data privacy and has inspired similar laws worldwide.
Simple explanation: GDPR is like a rulebook that says companies must treat your data with respect.
Real‑life example: A company must ask your permission before using your data.
School example: A school must protect student data and only use it for approved purposes.
Home example: You have the right to know how your data is being used.
Nigerian example: NDPR is based on GDPR principles.
Illustration:
GDPR Principles:
- Lawfulness, fairness, transparency
- Purpose limitation
- Data minimisation
- Accuracy
- Storage limitation
- Integrity and confidentiality
Mini summary: GDPR is a law that protects people's data and gives them control.
Definition: NDPR is Nigeria's data protection law – it regulates how personal data is collected, used, and protected in Nigeria.
Why is it important? It protects the privacy of Nigerian citizens and sets rules for organisations.
Simple explanation: NDPR is like a Nigerian rulebook for data – it tells companies how to handle your data safely.
Real‑life example: A Nigerian bank must follow NDPR to protect customer data.
School example: A Nigerian school must protect student data according to NDPR.
Home example: You have the right to know how your data is used by Nigerian companies.
Nigerian example: A fintech app must follow NDPR and get your consent before using your data.
Illustration:
NDPR Principles:
- Lawfulness
- Consent
- Purpose limitation
- Data quality
- Security
- Accountability
Mini summary: NDPR is Nigeria's data protection law – it sets rules for handling personal data.
Definition: Data lifecycle management is the process of managing data from creation to deletion – including storage, use, and archiving.
Why is it important? It ensures data is properly managed throughout its life.
Simple explanation: Data lifecycle is like a plant's life – it grows (is created), lives (is used), and eventually dies (is deleted).
Real‑life example: A company creates customer data, uses it for marketing, archives it after a few years, and then deletes it.
School example: A school creates student records, updates them each term, archives them after graduation, and deletes them after many years.
Home example: You take photos, store them, organise them, and eventually delete old ones.
Nigerian example: A bank creates transaction data, stores it, archives it, and eventually deletes it according to regulations.
Illustration:
Data Lifecycle:
+---------+ +---------+ +---------+ +---------+
| Create | → | Store | → | Use | → | Archive |
+---------+ +---------+ +---------+ +---------+
|
v
+---------+
| Delete |
+---------+
Mini summary: Data lifecycle management handles data from creation to deletion.
Definition: A data breach is an incident where data is accessed, stolen, or exposed without authorisation.
Why is it important? Data breaches can cause huge problems – identity theft, financial loss, and loss of trust.
Simple explanation: A data breach is like someone breaking into your house and stealing your things.
Real‑life example: A company's database is hacked, and customer data is stolen.
School example: A school's records are accessed by someone who shouldn't see them.
Home example: Your phone is lost, and someone sees your photos and contacts.
Nigerian example: A bank's customer data is leaked online.
Illustration:
+---------------------------------------+
| Data Breach |
+---------------------------------------+
| - Unauthorised access |
| - Data stolen or exposed |
| - Consequences: fines, trust loss |
+---------------------------------------+
Mini summary: A data breach is unauthorised access to data – it can have serious consequences.
Definition: Prevention includes strong security measures like encryption, access control, regular audits, and employee training.
Why is it important? Preventing breaches is better than dealing with the consequences.
Simple explanation: Prevention is like locking your doors and installing an alarm – you stop problems before they happen.
Real‑life example: A company uses strong passwords, encryption, and regular security audits.
School example: A school uses secure systems and trains staff on data protection.
Home example: You use strong passwords and keep your software updated.
Nigerian example: A bank uses encryption, access control, and regular security checks.
Illustration:
Prevention Measures:
- Encryption
- Strong passwords
- Access control
- Regular audits
- Employee training
- Monitoring
Mini summary: Preventing data breaches involves strong security measures and training.
Definition: Best practices for data governance include clear policies, defined roles, regular monitoring, and continuous improvement.
Why is it important? Following best practices ensures data is managed effectively and securely.
Simple explanation: Best practices are like a checklist – they help you do things the right way.
Real‑life example: A company has a clear data governance policy and updates it regularly.
School example: A school has policies for student data and reviews them each year.
Home example: Your family has rules for using devices and reviews them regularly.
Nigerian example: A bank follows NDPR best practices and updates its policies.
Illustration:
Best Practices:
- Clear policies
- Defined roles
- Regular monitoring
- Continuous improvement
- Employee training
- Incident response plan
Mini summary: Data governance best practices ensure data is managed effectively and securely.
Definition: A complete data governance framework includes policies, roles, processes, and technology to manage data.
Why is it important? This is what real organisations use to manage their data effectively.
Simple explanation: A governance framework is like a recipe – it tells you exactly what to do to manage data well.
Real‑life example: A company has a governance framework with policies for data quality, security, privacy, and compliance.
School example: A school has a governance framework for student data, staff data, and financial data.
Home example: Your family has a governance framework for personal information and devices.
Nigerian example: A bank has a governance framework that follows NDPR and includes security, privacy, and compliance.
Illustration:
+---------------------------------------+
| Data Governance Framework |
+---------------------------------------+
| +----------+ +----------+ |
| | Policies | | Roles | |
| +----------+ +----------+ |
| +----------+ +----------+ |
| | Processes| | Technology| |
| +----------+ +----------+ |
+---------------------------------------+
Mini summary: A data governance framework combines policies, roles, processes, and technology.
| Word | Simple Definition |
|---|---|
| Data Governance | Rules and policies for managing data. |
| Data Steward | A person responsible for managing data. |
| Data Security | Protecting data from unauthorised access. |
| Encryption | Scrambling data so only authorised people can read it. |
| Access Control | Limiting who can access data. |
| Data Privacy | Protecting personal information. |
| Compliance | Following laws and regulations. |
| GDPR | European data protection law. |
| NDPR | Nigeria Data Protection Regulation. |
| Data Breach | Unauthorised access to data. |
| Data Lifecycle | The journey of data from creation to deletion. |
This module introduces data governance and security – critical topics for data architects. Use real-world analogies (home security, family rules) to explain the concepts. Emphasise the importance of following laws like NDPR and GDPR. Encourage students to think about data protection in their daily lives.
Encourage your child to think about data privacy and security in their daily lives – passwords, privacy settings, and safe online behaviour. Discuss how laws like NDPR protect their data. Help them understand the importance of protecting personal information.
+---------------------------------------+
| Data Governance Framework |
+---------------------------------------+
| +----------+ +----------+ |
| | Policies | | Roles | |
| +----------+ +----------+ |
| +----------+ +----------+ |
| | Processes| | Tech | |
| +----------+ +----------+ |
+---------------------------------------+
| Feature | GDPR | NDPR |
|---|---|---|
| Region | Europe | Nigeria |
| Year | 2018 | 2019 |
| Fines | Up to €20 million | Up to ₦10 million |
| Key Principle | Consent | Lawfulness |
+---------------------+
| Security Measures |
+---------------------+
| - Encryption |
| - Strong passwords |
| - Access control |
| - Regular backups |
| - Firewalls |
| - Monitoring |
+---------------------+
You have completed Module 5 – "Data Governance, Security & Compliance"! You now know how to protect and manage data – from governance frameworks to security measures and compliance with laws like GDPR and NDPR.
Data governance is the foundation of data management – it ensures data is accurate, secure, and used responsibly. Data security protects data from threats, and compliance ensures you follow the rules.
These skills are essential for any data architect – you need to protect the data you manage.
Great work – you are now ready for Module 6!
| Term | Definition |
|---|---|
| 1. Data Governance | A. Protects personal information |
| 2. Data Steward | B. Scrambles data for protection |
| 3. Encryption | C. Rules for managing data |
| 4. Data Privacy | D. A person who manages data |
| 5. Compliance | E. Following laws and regulations |
Answers: 1‑C, 2‑D, 3‑B, 4‑A, 5‑E
Scenario 1: A company has suffered a data breach. What steps should they take to handle it and prevent future breaches?
Scenario 2: A Nigerian company wants to ensure it is compliant with NDPR. What policies and measures should they implement?
In groups, design a data governance framework for a Nigerian business – e.g., a bank, a school, or a fintech. Include policies, roles, security measures, privacy measures, and compliance with NDPR. Present your framework to the class.
Write a short essay on the importance of data governance and security in Nigeria. Include examples of how NDPR protects citizens and what organisations need to do to comply.
Design a Data Governance Plan: Choose an organisation (e.g., a school, a bank, a hospital). Design a data governance plan that includes policies, security measures, privacy measures, and compliance with relevant laws (NDPR, GDPR). Write a report and present it.
Create a data security checklist for a small business. Include items like encryption, access control, backups, employee training, and incident response. Explain why each item is important.
Design a complete data governance and security framework for a Nigerian fintech company. Include policies for data quality, data stewardship, security (encryption, access control), privacy (NDPR compliance), and incident response. Provide detailed explanations for each component.
Fill‑in‑the‑Blank: 1. Data governance, 2. data steward, 3. Data security, 4. Encryption, 5. Access control, 6. Data privacy, 7. Compliance, 8. GDPR, 9. NDPR, 10. data breach.
True/False: 1F, 2T, 3T, 4T, 5F, 6T, 7F, 8T, 9F, 10T.
Multiple Choice: 1A, 2A, 3A, 4A, 5A, 6A, 7A, 8A, 9A, 10A, 11A, 12A, 13A, 14A, 15A.
In Module 6, you will learn about advanced data architecture – including cloud architectures, data mesh, data fabric, and emerging trends like AI/ML. To prepare, think about how data architecture is evolving and how new technologies are changing the way we manage data.
Excellent work, future Data Architect! See you in Module 6!
Hello, future Data Architect! You have come a long way! You have learned about data, storage, modeling, integration, and governance. Now, we are going to look at the future of data architecture – including cloud computing, data mesh, and emerging technologies.
Data architecture is changing rapidly. New technologies like cloud computing allow us to store and process data at incredible scales. Data mesh is a new way of organising data that treats it as a product. And emerging trends like AI/ML are transforming how we use data.
In this module, you will learn about these advanced concepts and how they are shaping the future of data architecture.
Let's start with a story!
After this module, you will be able to:
Amina lived in a village that was becoming "smart" – they were getting solar panels, smart meters, and internet access. Everything was connected – lights, water pumps, and even the market.
But all this connected technology created a huge amount of data. Where would it all go? How would it be organised?
Amina's uncle, a data architect, said: "We need a modern data architecture. We can use the cloud to store all the data, a data mesh to organise it, and we can use AI to analyse it and make the village better."
Amina learned that data architecture is not just about databases – it's about using technology to solve problems and create a better future.
Now, let's explore these advanced concepts!
Definition: Cloud computing is the delivery of computing services – including storage, processing, and databases – over the internet.
Why is it important? Cloud computing allows you to access powerful resources without owning the hardware.
Simple explanation: Cloud computing is like renting a car instead of buying one – you pay for what you use, and you don't have to maintain it.
Real‑life example: Companies use AWS, Azure, or Google Cloud to store and process data.
School example: A school uses Google Drive to store assignments in the cloud.
Home example: You use iCloud to store photos and videos.
Nigerian example: Nigerian fintech companies use cloud services like AWS to host their applications.
Illustration:
+------------------+ +------------------+
| Your Computer | -------> | Cloud Services |
+------------------+ +------------------+
| (Client) | | (AWS, Azure, |
| | | GCP) |
+------------------+ +------------------+
Mini summary: Cloud computing provides computing services over the internet.
Definition: Cloud data platforms are services that provide data storage, processing, and analytics in the cloud – like AWS, Azure, and Google Cloud.
Why is it important? They provide powerful, scalable data solutions without the need for on-premises hardware.
Simple explanation: Cloud data platforms are like giant, fully-stocked kitchens – you can cook anything you want without having to buy all the equipment.
Real‑life example: A company uses AWS Redshift for its data warehouse.
School example: A school uses Azure for student data storage.
Home example: You use Google Cloud to back up your photos.
Nigerian example: A Nigerian bank uses Azure for its data analytics.
Illustration:
Cloud Data Platforms:
+---------+ +---------+ +---------+
| AWS | | Azure | | GCP |
+---------+ +---------+ +---------+
| Storage | | Storage | | Storage |
| Database| | Database| | Database|
| Analytics| | Analytics| | Analytics|
+---------+ +---------+ +---------+
Mini summary: Cloud data platforms provide scalable data services in the cloud.
Definition: Data mesh is a new approach to data architecture that treats data as a product, with decentralised ownership and domain-oriented design.
Why is it important? It solves the problems of centralised data architectures by giving teams ownership of their data.
Simple explanation: Instead of one central team managing all data, each business domain (like sales, marketing, finance) manages its own data as a product.
Real‑life example: A company's sales team owns sales data, marketing owns marketing data, and finance owns financial data.
School example: The math department owns math grades, the science department owns science grades.
Home example: Each family member manages their own personal data.
Nigerian example: A Nigerian bank uses data mesh so each department manages its own customer data.
Illustration:
+---------------------------------------+
| Data Mesh |
+---------------------------------------+
| +--------+ +--------+ +--------+ |
| | Sales | | Marketing| | Finance| |
| | Domain | | Domain | | Domain | |
| +--------+ +--------+ +--------+ |
+---------------------------------------+
Mini summary: Data mesh decentralises data ownership to individual domains.
Definition: Data fabric is an architecture that connects data across different environments – including on-premises, cloud, and edge – with a unified layer.
Why is it important? It provides a unified view of data, no matter where it is stored.
Simple explanation: Data fabric is like a magical bridge that connects all your data sources, making them work together seamlessly.
Real‑life example: A company uses a data fabric to connect data from cloud, on-premises, and IoT devices.
School example: A school connects data from different systems – student records, library, and cafeteria.
Home example: You connect your phone, computer, and smart TV to share data.
Nigerian example: A Nigerian company uses a data fabric to connect data from branches across the country.
Illustration:
+---------------------------------------+
| Data Fabric |
+---------------------------------------+
| +--------+ +--------+ +--------+ |
| | Cloud | | On-prem| | Edge | |
| | Data | | Data | | Data | |
| +--------+ +--------+ +--------+ |
+---------------------------------------+
Mini summary: Data fabric connects data across different environments.
Definition: Data mesh is about decentralising ownership; data fabric is about connecting data across environments.
Why is it important? They are complementary – you can use both together.
Simple explanation: Data mesh is about who owns the data; data fabric is about how data is connected.
Real‑life example: A company uses data mesh for ownership and data fabric for integration.
School example: Data mesh for departments, data fabric for connecting all school systems.
Home example: Data mesh for family members, data fabric for connecting all devices.
Nigerian example: A Nigerian company uses both for better data management.
Illustration:
Data Mesh: Decentralised ownership
Data Fabric: Unified connectivity
Mini summary: Data mesh focuses on ownership; data fabric focuses on connectivity.
Definition: AI (Artificial Intelligence) and ML (Machine Learning) are technologies that use data to make predictions and decisions.
Why is it important? AI/ML is transforming how we use data – from recommendations to fraud detection.
Simple explanation: AI/ML is like teaching a computer to learn from data, just like you learn from examples.
Real‑life example: Netflix uses ML to recommend movies.
School example: A school uses ML to predict student performance.
Home example: Smart assistants use AI to answer your questions.
Nigerian example: A Nigerian fintech uses ML for fraud detection.
Illustration:
Data → AI/ML Model → Predictions
(Input) → (Learning) → (Output)
Mini summary: AI/ML uses data to make predictions and decisions.
Definition: Data architecture for AI/ML must support data ingestion, storage, processing, and model deployment.
Why is it important? AI/ML requires large amounts of clean, well-organised data.
Simple explanation: AI/ML is like cooking – you need the right ingredients (data) and a good kitchen (architecture).
Real‑life example: A company builds a data pipeline to feed data to its ML models.
School example: A school collects student data to build a predictive model.
Home example: You collect data from your smart devices to train a home automation model.
Nigerian example: A Nigerian company builds a data platform for AI/ML analytics.
Illustration:
+----------+ +----------+ +----------+
| Ingestion| → | Storage | → | Training |
+----------+ +----------+ +----------+
|
v
+----------+
|Deployment|
+----------+
Mini summary: Data architecture for AI/ML supports the entire lifecycle of models.
Definition: Real-time analytics is the ability to analyse data as it arrives, providing immediate insights.
Why is it important? It enables instant decision-making – like fraud detection or live traffic updates.
Simple explanation: Real-time analytics is like watching a live sports game – you see what's happening right now.
Real‑life example: Uber uses real-time analytics to match drivers and riders.
School example: A live quiz shows scores in real-time.
Home example: A smart thermostat updates the temperature in real-time.
Nigerian example: A Nigerian fintech uses real-time analytics for fraud detection.
Illustration:
Data Arrives → Process → Insights
(Real-time) → (Fast) → (Immediate)
Mini summary: Real-time analytics processes data as it arrives for immediate insights.
Definition: Edge computing is processing data closer to where it is created – at the "edge" of the network, rather than in a centralised cloud.
Why is it important? It reduces latency (delay) and bandwidth usage – useful for IoT devices.
Simple explanation: Edge computing is like having a mini-kitchen in your house instead of going to a central restaurant – faster and more convenient.
Real‑life example: Self-driving cars process data at the edge (in the car) for immediate decisions.
School example: A school uses edge computing for real-time attendance tracking.
Home example: A smart home hub processes data locally instead of sending it to the cloud.
Nigerian example: A Nigerian company uses edge computing for IoT solutions.
Illustration:
+----------+ +----------+
| Edge | -------> | Cloud |
| (Local) | | (Central)|
+----------+ +----------+
| Fast | | Powerful |
| Low | | Scalable |
| Latency | | |
+----------+ +----------+
Mini summary: Edge computing processes data closer to the source for speed and efficiency.
Definition: Hybrid cloud uses a mix of on-premises and cloud services; multi-cloud uses multiple cloud providers.
Why is it important? They provide flexibility, redundancy, and cost optimisation.
Simple explanation: Hybrid cloud is like having a home kitchen and also eating out – you choose what's best for each meal. Multi-cloud is like having subscriptions to multiple restaurants – you pick the one you like for each occasion.
Real‑life example: A company uses on-premises for sensitive data and cloud for scalable analytics.
School example: A school uses local servers for student records and cloud for online learning.
Home example: You store personal files locally and use the cloud for backups.
Nigerian example: A Nigerian bank uses a hybrid approach for data security and scalability.
Illustration:
Hybrid Cloud: On-premises + Cloud
Multi-Cloud: Cloud + Cloud (e.g., AWS + Azure)
Mini summary: Hybrid and multi-cloud provide flexibility and choice.
Definition: Data observability is the ability to monitor, understand, and troubleshoot data systems.
Why is it important? It helps identify and fix issues before they cause problems.
Simple explanation: Data observability is like having a dashboard that shows you the health of your data systems.
Real‑life example: A company monitors data pipelines for delays or errors.
School example: A school monitors data systems to ensure student records are up-to-date.
Home example: You monitor your smart home devices to ensure they are working.
Nigerian example: A Nigerian fintech monitors its data pipelines for fraud detection.
Illustration:
+---------------------------------------+
| Data Observability |
+---------------------------------------+
| - Monitor data pipelines |
| - Detect anomalies |
| - Ensure data quality |
| - Alert on issues |
+---------------------------------------+
Mini summary: Data observability monitors the health of data systems.
Definition: Data-as-a-product is a mindset that treats data as a valuable product that should be designed, built, and delivered with the same care as any other product.
Why is it important? It encourages data quality, usability, and value creation.
Simple explanation: Data-as-a-product means treating data like a toy – you design it well, make it fun to use, and deliver it with care.
Real‑life example: A company creates a data product that provides customer insights to its teams.
School example: A school creates a data product that shows student performance trends.
Home example: You create a data product like a family photo album.
Nigerian example: A Nigerian company creates data products for its customers.
Illustration:
Data-as-a-Product:
+---------------------------------------+
| - Designed for users |
| - High quality |
| - Delivered with care |
| - Continuously improved |
+---------------------------------------+
Mini summary: Data-as-a-product treats data as a valuable product.
Definition: Sustainability in data architecture means designing systems that are energy-efficient and environmentally friendly.
Why is it important? Data centres consume a lot of energy – sustainable practices reduce environmental impact.
Simple explanation: Sustainability is like turning off lights when you leave a room – it saves energy and helps the planet.
Real‑life example: A company uses energy-efficient cloud data centres.
School example: A school uses energy-efficient servers.
Home example: You use energy-efficient devices and turn them off when not in use.
Nigerian example: A Nigerian company uses green data centres.
Illustration:
Sustainability in Data:
- Energy-efficient hardware
- Optimised workloads
- Renewable energy
- Reduce, reuse, recycle
Mini summary: Sustainability in data architecture focuses on energy efficiency and environmental responsibility.
Definition: The future of data architecture includes trends like AI automation, real-time everything, and quantum computing.
Why is it important? Understanding trends helps you prepare for the future.
Simple explanation: The future is like a video game – new levels, new challenges, and new tools.
Real‑life example: AI-powered data management, automatic data integration.
School example: AI tutors, real-time analytics for student performance.
Home example: Smart homes that anticipate your needs.
Nigerian example: Nigerian companies adopting AI and cloud technologies.
Illustration:
Future Trends:
- AI-powered automation
- Real-time analytics
- Quantum computing
- Data mesh and fabric
- Edge computing
- Sustainability
Mini summary: The future of data architecture includes AI, real-time, and quantum computing.
Definition: A modern data architecture combines cloud, data mesh, AI/ML, real-time, and governance into a cohesive system.
Why is it important? This is what real-world organisations are building today.
Simple explanation: It's like building a smart city – all systems work together to create a better environment.
Real‑life example: A company uses cloud for storage, data mesh for ownership, AI for insights, and real-time analytics for operations.
School example: A school uses cloud for data, data mesh for departments, AI for predictions, and real-time for attendance.
Home example: You use cloud for storage, data mesh for family members, AI for automation, and real-time for devices.
Nigerian example: A Nigerian company builds a modern data architecture with cloud, AI, and data mesh.
Illustration:
+---------------------------------------+
| Modern Data Architecture |
+---------------------------------------+
| - Cloud (AWS, Azure, GCP) |
| - Data Mesh (decentralised) |
| - Data Fabric (connected) |
| - AI/ML (predictions) |
| - Real-time (immediate) |
| - Governance (rules) |
+---------------------------------------+
Mini summary: A modern data architecture combines cloud, mesh, AI, and real-time.
| Word | Simple Definition |
|---|---|
| Cloud Computing | Delivering computing services over the internet. |
| Data Mesh | Decentralised data ownership by domain. |
| Data Fabric | Connecting data across different environments. |
| AI/ML | Using data to make predictions and decisions. |
| Real-Time Analytics | Analysing data as it arrives. |
| Edge Computing | Processing data closer to the source. |
| Hybrid Cloud | Mix of on-premises and cloud. |
| Multi-Cloud | Using multiple cloud providers. |
| Data Observability | Monitoring data system health. |
| Data-as-a-Product | Treating data as a valuable product. |
This module introduces advanced concepts and future trends. Use real-world examples and case studies to make the concepts tangible. Encourage students to think about how these technologies are applied in Nigeria. The goal is to prepare students for the evolving landscape of data architecture.
Encourage your child to think about how cloud, AI, and real-time technologies affect their daily lives – from social media to smart devices. Discuss how data architecture is shaping the future of Nigeria and the world.
| Platform | Storage | Database | Analytics |
|---|---|---|---|
| AWS | S3 | RDS, DynamoDB | Redshift, Athena |
| Azure | Blob Storage | SQL Database, Cosmos DB | Synapse Analytics |
| GCP | Cloud Storage | Cloud SQL, Firestore | BigQuery |
| Feature | Data Mesh | Data Fabric |
|---|---|---|
| Focus | Decentralised ownership | Unified connectivity |
| Goal | Domain-owned data | Integrated data |
| Example | Sales domain owns sales data | Connect cloud and on-prem data |
+---------------------------------------+
| Modern Data Architecture |
+---------------------------------------+
| +----------+ +----------+ |
| | Cloud | | Edge | |
| | (AWS) | | (Local) | |
| +----------+ +----------+ |
| +----------+ +----------+ |
| | Data Mesh| | Data | |
| | (Domain) | | Fabric | |
| +----------+ +----------+ |
| +----------+ +----------+ |
| | AI/ML | | Real-time| |
| +----------+ +----------+ |
+---------------------------------------+
You have completed Module 6 – "Advanced Data Architecture"! You now know about cloud computing, data mesh, data fabric, AI/ML, real-time analytics, and emerging trends. You have a vision of the future of data architecture.
This is the final module of the theory portion of the course. You now have a comprehensive understanding of data architecture – from the basics to advanced concepts. You are ready to apply these skills in real-world scenarios.
Congratulations! You are now ready for the Capstone Project!
| Term | Definition |
|---|---|
| 1. Cloud | A. Decentralised ownership |
| 2. Data Mesh | B. Connecting data across environments |
| 3. Data Fabric | C. Services over the internet |
| 4. AI/ML | D. Processing data as it arrives |
| 5. Real-time | E. Using data for predictions |
Answers: 1‑C, 2‑A, 3‑B, 4‑E, 5‑D
Scenario 1: A Nigerian fintech company wants to modernise its data architecture. They want to use cloud, data mesh, and AI/ML. Design a modern data architecture for them.
Scenario 2: A school wants to use real-time analytics to track student attendance and performance. What architecture would you recommend?
In groups, design a modern data architecture for a Nigerian organisation of your choice (e.g., bank, hospital, school). Include cloud, data mesh, AI/ML, real-time, and governance. Present your architecture to the class.
Write a report on how data architecture is evolving in Nigeria. Include cloud adoption, AI/ML trends, and challenges. Provide recommendations for organisations.
Design a Modern Data Architecture: Choose an organisation (e.g., a fintech, a hospital, a school). Design a complete modern data architecture with cloud, data mesh, AI/ML, real-time, and governance. Write a report and present it.
Write a cloud migration plan for a Nigerian company. Include steps for moving data to the cloud, choosing the right platform, and ensuring security and compliance.
Design a complete data architecture for a Nigerian smart city project. Include cloud, data mesh, data fabric, AI/ML, real-time analytics, edge computing, and sustainability. Provide detailed explanations and diagrams.
Fill‑in‑the‑Blank: 1. Cloud, 2. Data mesh, 3. Data fabric, 4. AI/ML, 5. Real-time, 6. Edge, 7. Hybrid, 8. Multi, 9. Data observability, 10. Data-as-a-product.
True/False: 1F, 2T, 3T, 4F, 5F, 6F, 7F, 8T, 9T, 10T.
Multiple Choice: 1B, 2B, 3A, 4A, 5A, 6B, 7B, 8B, 9A, 10A, 11A, 12A, 13B, 14A, 15A.
You have now completed all the modules of the Certified Data Architecture Specialist course! The next step is the Capstone Project, where you will apply everything you have learned to a real-world scenario.
In the Capstone Project, you will design a complete data architecture for a case study organisation. You will need to demonstrate your knowledge of data storage, modeling, integration, governance, security, and modern architecture trends.
Congratulations, future Data Architect! You are now ready to take on the Capstone Project!