Book Image

Connecting the Data: Data Integration Techniques for Building an Operational Data Store (ODS)

By : Angelo Bobak

Book Image

Connecting the Data: Data Integration Techniques for Building an Operational Data Store (ODS)

By: Angelo Bobak

Overview of this book

When organizations change or enhance their internal structures, business data integration is a complex problem that they must resolve. This book describes the common hurdles you might face while working with data integration and shows you various ways to overcome these challenges. The book begins by explaining the foundational concepts of ODS. Once familiar with schema integration, you?ll learn how to reverse engineer each data source for creating a set of data dictionary reports. These reports will provide you with the metadata necessary to apply the schema integration process. As you progress through the chapters, you will learn how to write scripts for populating the source databases and spreadsheets, as well as how to use reports to create Extract, Transform, and Load (ETL) specifications. By the end of the book, you will have the knowledge necessary to design and build a small ODS.

Preface

Who this book is for

What this book covers

To get the most out of this book

Download the example code files

Download the color images

Conventions used

Free Chapter

Section 1: Site Reliability Engineering – A Prescriptive Way to Implement DevOps

Section 1: Site Reliability Engineering – A Prescriptive Way to Implement DevOps

Chapter 1: DevOps, SRE, and Google Cloud Services for CI/CD

Chapter 1: DevOps, SRE, and Google Cloud Services for CI/CD

Understanding DevOps, its evolution, and life cycle

SRE's evolution; technical and cultural practices

Cloud-native approach to implementing DevOps using Google Cloud

Points to remember

Further reading

Chapter 2: SRE Technical Practices – Deep Dive

Chapter 2: SRE Technical Practices – Deep Dive

Defining reliability expectations via SLOs

Understanding error budgets

Eliminating toil through automation

Illustrating the impact of SLAs, SLOs, and error budgets relative to SLI

Points to remember

Further reading

Chapter 3: Understanding Monitoring and Alerting to Target Reliability

Chapter 3: Understanding Monitoring and Alerting to Target Reliability

Understanding monitoring

Points to remember

Further reading

Chapter 4: Building SRE Teams and Applying Cultural Practices

Chapter 4: Building SRE Teams and Applying Cultural Practices

Building SRE teams

Incident management

Psychological safety

Sharing vision and knowledge and fostering collaboration

Points to remember

Further reading

Section 2: Google Cloud Services to Implement DevOps via CI/CD

Section 2: Google Cloud Services to Implement DevOps via CI/CD

Chapter 5: Managing Source Code Using Cloud Source Repositories

Chapter 5: Managing Source Code Using Cloud Source Repositories

Technical requirements

Introducing the key features

One-way sync from GitHub/Bitbucket to CSR

Common operations in CSR

Hands-on lab – integrating with Cloud Functions

Further reading

Chapter 6: Building Code Using Cloud Build, and Pushing to Container Registry

Chapter 6: Building Code Using Cloud Build, and Pushing to Container Registry

Technical requirements

Key terminology (prerequisites)

Understanding the need for automation

Building and creating container images – Cloud Build

Managing build artifacts – Container Registry

Hands-on lab – building, creating, pushing, and deploying a container to Cloud Run using Cloud Build triggers

Points to remember

Further reading

Chapter 7: Understanding Kubernetes Essentials to Deploy Containerized Applications

Chapter 7: Understanding Kubernetes Essentials to Deploy Containerized Applications

Technical requirements

Kubernetes – a quick introduction

Kubernetes cluster anatomy

Kubernetes objects

Scheduling and interacting with Pods

Kubernetes deployment strategies

Points to remember

Further reading

Chapter 8: Understanding GKE Essentials to Deploy Containerized Applications

Chapter 8: Understanding GKE Essentials to Deploy Containerized Applications

Technical requirements

Google Kubernetes Engine (GKE) – introduction

GKE – core features

GKE Autopilot – hands-on lab

Points to remember

Further reading

Chapter 9: Securing the Cluster Using GKE Security Constructs

Chapter 9: Securing the Cluster Using GKE Security Constructs

Technical requirements

Essential security patterns in Kubernetes

Hardening cluster security in GKE

Points to remember

Further reading

Chapter 10: Exploring GCP Cloud Operations

Chapter 10: Exploring GCP Cloud Operations

Cloud Monitoring

Binding SRE and Cloud Operations

Points to remember

Further reading

Mock Exam 1

Total Number of Questions: 50

Mock Exam 2

Total Number of Questions: 50

Other Books You May Enjoy

Other Books You May Enjoy

Packt is searching for authors like you

Leave a review - let other readers know what you think

Appendix: Getting Ready for Professional Cloud DevOps Engineer Certification

Appendix: Getting Ready for Professional Cloud DevOps Engineer Certification

Cloud Deployment Manager

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Cloud Trace

A trace is a collection of spans. A span is an object that wraps latency-specific metrics and other contextual information around a unit of work in an application. Cloud Trace is a distributed tracing system that captures latency data from an application, tracks the request's propagation, retrieves real-time performance insights, and displays the results in Google Cloud Console. This latency information can be either for a single request or can be aggregated for the entire application. This information helps us identify performance bottlenecks.

Additionally, Cloud Trace can automatically analyze application traces that might reflect recent changes to the application's performance, identify degradations from latency reports, capture traces from containers, and create alerts as needed.

Cloud Trace's language-specific SDKs are available for Java, Node.js, Ruby, and Go. These SDKs can analyze projects running on VMs. It is not necessary for these VMs to...