Skip to content
Projects

sonhmai/data-systems-design

View on GitHub

sonhmai/data-systems-design has 84 GitHub stars and 24 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-15 04:44 UTC. Last push 2025-08-14.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
0
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

System Design, Solution Architecture, Data Systems Practice

Data

README.md

Original

= Data Systems Design and Implementation :idprefix: :idseparator: - :sectanchors: :sectlinks: :sectnumlevels: 6 :sectnums: :toc: macro :toclevels: 6 :toc-title:

Collection of useful notes, readings, videos, codes related to data systems design

toc::[]

== System Design Resources

=== Learning Resources Repos

=== Books

=== Blogs

Replication

Performance

CAP

  • https://www.youtube.com/watch?v=srOgpXECblk[Google I/O 2009 - Transactions Across Datacenters]: distributed systems, transactions, fault-tolerance, consistency, replication, sharding, two phase commit, consensus protocol with App Engine datastore use case.

=== Video Courses

== Data Architecture

Blogs

Videos

== Data Storage Terms

  • Table Formats (Iceberg, Hudi, Delta, OneTable, etc.).
  • Features (ACID transaction, Schema Evolution, Upsert, Time Travel, etc.).
  • Tech ( Copy On Write vs Merge On Read, Compaction, Vacuum, OCC (Optimistic Concurrency Control), MVCC (Multiversion Concurrency Control) )

Blogs and Videos

RFCs

== Data Consumption

Blogs

== Data Processing Blogs

Papers

Projects

== Data Governance Metadata management, data quality, data veracity, data security, data lineage, etc.

=== Data Quality

Blogs

Papers

Best Practices

  • too little data quality alerts let important issues go unresolved.
  • too many alerts overwhelms and might make the most important ones go un-noticed.
  • statistical modeling techniques (PCA, etc.) can be used to reduce computation resource for quality checks.
  • separate anomaly detection from anomaly scoring and alerting strategy.

Common Issues

  • issues in metadata category (data availability, data freshness, schema changes, data completeness) -> can be obtained without checking dataset content
  • issues in semantic category(dataset content: column value nullability, duplication, distribution, exceptional values, etc.) -> needs data profiling

=== Data Lineage Blogs

=== Data Security, Compliance GDPR, CCPA, PII Protection, etc.

== Data Integration

Blogs

== Machine Learning

== Platform and Infra

Kubernetes

Terraform

Network

== Testing

=== Deterministic Simulation Testing (DST)

Videos

== Operations

Observability, Monitoring

Incidents

== Interview Resources

== Databricks

Architecture

Data Pipelines

Spark and Databricks Compute

Delta Lake

  • Managing Recalls with Barcode Traceability on the Delta Lake
  • Creating a Spark Streaming ETL pipeline with Delta Lake at Gousto
    • issues and solutions ** costly Spark op MSCK REPAIR TABLE because it needs to scan table' sub-tree in S3 bucket. -> use ALTER TABLE ADD PARTITION instead. ** not caching dataframes for multiple usages. -> use cache ** rewriting all destination table incl. old partitions when having a new partition. -> append new partition to destination. ** architecture (waiting for CI, Airflow triggering, EMR spinning up, job run, working with AWS console for logs) slowing down development. Min feedback loop of 20 minutes. -> move away from EMR, adopt a platform allowing to have complete control of clusters and prototyping.
    • Databricks Pros ** Reducing ETL time, latency from 2 hours to 15s by using streaming job and delta architecture. ** Spark Structured Streaming Autoloader helps manage infra (setting up bucket noti, SNS and SQS in the background). ** Notebook helps prototype on/ explore production data, debug with traceback and logs interactively. Then CICD to deploy when code is ready. This helps reduce dev cycle from 20 mins to seconds. ** Costs remain the same as before Databricks. (using smaller instances with streaming cluster, which compensated for DBx higher costs vs EMR). ** Reducing complexity in codebase and deployment (no Airflow). ** Better ops: performance dashboards, Spark UI, reports.
    • Other topics: DBT for data modeling, Redshift, SSOT.
  • Data Modeling Best Practices & Implementation on a Modern Lakehouse

Governance

Backfilling

== Performance

Papers

== Databases

=== LSM Tree Storage Engine

== Serverless Databases

Collections of resources of how serverless databases work

=== Papers

  1. https://dx.doi.org/10.1145/3035918.3056101[A. Verbitski et al., “Amazon Aurora,” Proceedings of the 2017 ACM International Conference on Management of Data.]
  2. P. Antonopoulos et al., “Socrates,” Proceedings of the 2019 International Conference on Management of Data.
  3. W. Cao et al., “PolarDB Serverless,” Proceedings of the 2021 International Conference on Management of Data.

=== Blogs

  1. https://neon.tech/blog/how-we-scale-an-open-source-multi-tenant-storage-engine-for-postgres-written-rust[Neon. How we scale an open source, multi-tenant storage engine for Postgres written in Rust].