Multiple ingestion patterns
Batch files, PostgreSQL CDC, REST APIs, and streaming events all feed the platform through patterns appropriate to each source.
A production-style AWS data engineering platform built to demonstrate how I design, build, test, operate, troubleshoot, and explain a modern data system from source to analytics.
The Problem
Northstar exists to demonstrate an entire data platform rather than a collection of isolated AWS exercises.
The project covers operational data modeling, batch and streaming ingestion, incremental processing, transformation, data quality, lakehouse architecture, warehousing, orchestration, observability, security, deployment, and cost management.
The goal is not simply to show that a service was configured. The goal is to show that I can explain why it was chosen, verify that it works, diagnose failures, and defend the tradeoffs involved.
Synthetic Business
The platform operates on a deterministic synthetic e-commerce company selling outdoor products. The simulator will generate customers, products, warehouses, orders, order lines, web events, payments, refunds, inventory, shipments, marketing activity, and support data.
The data is intentionally imperfect. Late records, duplicates, invalid relationships, malformed values, schema changes, stockouts, refunds, shipment delays, seasonal demand, and other realistic conditions create problems the pipelines must detect and handle.
Architecture
PostgreSQL / RDS REST APIs Event Simulator
| | |
DMS / CDC Lambda / Python Kinesis
| | |
+--------------------+--------------------+
|
v
S3 RAW
|
Glue Catalog
|
Glue / PySpark
|
+----------+----------+
| |
Quarantine S3 Curated
|
Parquet / Iceberg
|
+------------+------------+
| |
Athena Redshift
|
dbt
|
Analytical Models
|
Portfolio DataIAM, KMS, Secrets Manager, CloudWatch, messaging, orchestration, Terraform, Docker, CI/CD, Cognito, API Gateway, and Lambda surround the core data flow to provide security, deployment, observability, and controlled access.
Engineering Scope
Batch files, PostgreSQL CDC, REST APIs, and streaming events all feed the platform through patterns appropriate to each source.
SQL, Python, Glue, and PySpark handle validation, standardization, deduplication, enrichment, quarantine, and curated data output.
S3, Parquet, Apache Iceberg, Athena, Redshift, and dbt demonstrate both lake-oriented and warehouse-oriented analytical architecture.
Orchestration, idempotency, monitoring, alerting, testing, data quality, failure recovery, and cost controls are treated as core engineering requirements.
IAM, encryption, secrets management, controlled APIs, temporary reviewer access, and infrastructure as code are built into the platform rather than added afterward.
Architecture decisions, source code, tests, lineage, pipeline history, data-quality evidence, and engineering tradeoffs will be visible through the portfolio.
Build Status
The repository and development environment are established, and the public portfolio shell is now being built. Infrastructure and data-platform components are added only after they can be implemented, tested, observed, and explained.
Portfolio Evidence
The repository contains the infrastructure, application code, engineering documentation, tests, and Git history as Northstar develops from an empty AWS account into a complete data platform.