Why this is in my collection
From the publisher:
The missing expert-led manual for the AWS ecosystem — go from foundations to building data engineering pipelines effortlesslyKey FeaturesLearn about common data architectures and modern approaches to generating value from big dataExplore AWS tools for ingesting, transforming, and consuming data, and for orchestrating pipelinesLearn how to architect and implement data lakes and data lakehouses for big data analytics from a data lakes expertBook DescriptionWritten by a Senior Data Architect with over twenty-five years of experience in the business, Data Engineering for AWS is a book whose sole a
Highlights
- Pipelines decompose into ingest–transform–consume stages — Eagar's architecture-first framing shows the stage pattern is stable even though the AWS service behind each stage keeps changing; the durable layer is the pattern, the service catalog is churn.
- Lake and lakehouse zones are a modeling decision — raw/curated/consumption zoning is a lightweight structural model imposed on storage, and it is that structure (not the S3 bucket) that makes the lake usable.
- Orchestration is where the rules live — scheduling, dependencies, and quality gates in Step Functions or Glue workflows are executable rules around the data flow; the often-forgotten third pillar made concrete in cloud tooling.
- Cataloging and permissions before consumption — Glue Catalog and Lake Formation put metadata and access rules in front of every consumer, a reminder that governance is infrastructure, not paperwork.
- A service-by-service book ages fast; its patterns don't — reading it as a catalog of 2021 AWS services dates it, reading it as a catalog of pipeline patterns keeps it useful; a live demonstration of why MDDE bets on the model layer.
Highlights on this page are generated with the help of AI.