You're reading from Data Engineering with AWS Acquire the skills to design and build AWS-based data transformation pipelines like a pro

Product type Paperback

Published in Oct 2023

Publisher Packt

ISBN-13 9781804614426

Length 636 pages

Edition 2nd Edition

Tools

AWS

Concepts

Data Engineering

Author (1):

Gareth Eagar

View More author details

Table of Contents (24) Chapters

Preface

1. Section 1: AWS Data Engineering Concepts and Trends

2. An Introduction to Data Engineering FREE CHAPTER

3. Data Management Architectures for Analytics

4. The AWS Data Engineer’s Toolkit

5. Data Governance, Security, and Cataloging

6. Section 2: Architecting and Implementing Data Engineering Pipelines and Transformations

7. Architecting Data Engineering Pipelines

8. Ingesting Batch and Streaming Data

9. Transforming Data to Optimize for Analytics

10. Identifying and Enabling Data Consumers

11. A Deeper Dive into Data Marts and Amazon Redshift

12. Orchestrating the Data Pipeline

13. Section 3: The Bigger Picture: Data Analytics, Data Visualization, and Machine Learning

14. Ad Hoc Queries with Amazon Athena

15. Visualizing Data with Amazon QuickSight

16. Enabling Artificial Intelligence and Machine Learning

17. Section 4: Modern Strategies: Open Table Formats, Data Mesh, DataOps, and Preparing for the Real World

18. Building Transactional Data Lakes

19. Implementing a Data Mesh Strategy

20. Building a Modern Data Platform on AWS

21. Wrapping Up the First Part of Your Learning Journey

22. Other Books You May Enjoy

23. Index

What does it mean for a data lake to be transactional?

Transactional data lakes is a common way to refer to the abilities enabled by these new table formats, but what does that mean?

Let’s start by looking at the definition of a database transaction in general, from Wikipedia (https://en.wikipedia.org/wiki/Database_transaction):

”A database transaction symbolizes a unit of work, performed within a database management system (or similar system) against a database, that is treated in a coherent and reliable way independent of other transactions.”

What this means is that you have the ability to update a database in a way that may potentially make multiple updates as part of the transaction, and you have the guarantee that all the individual updates will work and be applied consistently, or the whole transaction will fail. That means that if there are five updates as part of the transaction, and the third update fails, then the two previous...