TLDR Data 2026-03-16
Embedding-Driven Feed 🗂️, Scaling Spotify Wrapped ✨, MCP Isn’t Dead 🤖
Trade hours of manual engineering for pre-built connectors. (Sponsor)
Instead of manually connecting investment data that arrives in multiple formats and constantly maintaining it, you could be putting that data to work. The Aquata® Data Platform replaces months of tedious ETL engineering with pre-built connectors that automatically normalize and validate that data for you, with:
- Pre-built connectors to custodians, fund admins, market data, and cloud platforms
- Domain-specific investment data models
- Automated schema mapping and validation
- Faster onboarding of new data sources
Meet the data connectivity layer for investment teams. Get a free 30-day trial.
Engineering the next generation of LinkedIn's Feed (12 minute read)
LinkedIn redesigned its feed by introducing a unified retrieval system powered by LLM-generated embeddings and a sequential Generative Recommender (GR) model using causal attention transformers to model chronological interaction sequences, capturing deeper semantic relevance and professional trajectories without relying on demographic features.
Inside the Archive: The Tech Behind Your 2025 Wrapped Highlights (12 minute read)
Spotify's Wrapped Archive identifies up to five “remarkable days” in each user's listening history using heuristics and data pipelines, then generates personalized narratives grounded in the data using a fine-tuned LLM. To scale to ~1.4 billion reports, Spotify distilled a smaller model, built distributed pipelines and storage optimized for concurrency, and used automated LLM-based evaluation to ensure accuracy, safety, and consistency at launch.
How did YouTube engineers build CI/CD for data pipelines? (8 minute read)
YouTube's data warehouse processes multiple exabytes daily across thousands of time-partitioned pipelines, demanding robust CI/CD practices to address dynamic data schemas, intricate dependencies, and distributed observability. Its framework leverages test configuration isolation, dependency-aware configuration rewriting, sampling to reduce test data by up to 99.9%, and a centralized metadata hub for enhanced collaboration and traceability. This approach delivers up to 50% faster integration investigations, shrinks schema deployment cycles from months to weeks, and improves overall data quality and cross-team velocity.
Test Smarter, Not Harder: Risk-Based Data Quality Without Pipeline Paralysis (11 minute read)
Vinted adopted a risk-based testing approach inspired by prioritizing impact and informational quality, tagging dbt tests with impact/frequency levels, excluding low-impact ones from main dbt builds, and running high-impact tests daily via Airflow while monitoring others weekly or via alerts.
MCP is Dead; Long Live MCP! (9 minute read)
Claims that MCP is obsolete are mostly hype: while CLIs can sometimes save tokens, they face similar context and usability limits when tools are custom. For organizations, MCP remains valuable because it provides structure, security, telemetry, and centralized tooling needed to run AI agents reliably at scale.
Your Data Model Isn't Broken, Part I: Why Refactoring Beats Rebuilding (12 minute read)
Big-bang rewrites of legacy data systems, often triggered by new leadership or platform migrations, consistently underestimate essential business complexity and the institutional knowledge embedded in existing models. Refactoring (small, incremental improvements with rigorous testing) preserves critical, undocumented logic and avoids the 45% average IT project overrun and 56% value shortfall documented by McKinsey. Treat legacy complexity as indispensable knowledge, methodically improve it, and avoid discarding years of hard-earned operational understanding.
The Context Problem (25 minute read)
AI vendors monetize “context” as a billing unit, charging by token count rather than the quality or coherence of information processed, with prices varying up to 360x between major models (e.g., GPT-5.4 Pro at $180/million output tokens vs. Grok 4.1 Fast at $0.50). Expanding context windows often degrades model performance unless context is well-structured. Context engineering, neurosymbolic AI, and knowledge graphs can cut token usage by up to 80%. Invest in explicit semantic structures and context governance to avoid skyrocketing AI spend and unreliable outputs.
KIP-1150 Accepted, and the Road Ahead (8 minute read)
KIP-1150's approval brings Diskless Topics to Apache Kafka, enabling compute-storage separation by shifting replication and storage from broker disks to cloud object storage. This transformation slashes total cost of ownership by up to 80%, eliminates inter-AZ replication traffic, and allows for instant elasticity without client changes. This major change positions Kafka as a truly cloud-native streaming standard.
Dolt (GitHub Repo)
Dolt is an open-source MySQL-compatible database with built-in Git-style version control. It lets you branch, diff, merge, commit, and clone tables and schema just like code in Git, while remaining compatible with standard SQL tools. Useful for data collaboration, reproducibility, auditing, and debugging, you can inspect historical states of datasets and resolve row-level merge conflicts directly in SQL.
OpenViking (GitHub Repo)
OpenViking is an open-source context database designed specifically for AI agents (such as OpenClaw). OpenViking unifies the management of context (memory, resources, and skills) that Agents need through a file system paradigm, enabling hierarchical context delivery and self-evolving.
Data management principles for resilient systems (13 minute read)
True resilience arises from how systems interact under stress, not from isolated data assets or individual component strength. Effective data management demands that data seamlessly flows into decision-capable systems with well-designed integrations, rapid governance pathways under duress, and clear operational authority. System diagrams often mask hidden dependencies and integration weaknesses, which only manifest during crises. Investing in integration-first design, real stress simulations, and adaptive governance ensures technical and organizational optionality.
Evolutionary Database Design (31 minute read)
Evolutionary database design enables agile teams to iteratively evolve database schemas alongside application code by leveraging automated migration scripts, rigorous version control, and continuous integration pipelines. Key practices include treating all schema and data changes as versioned migrations, automating database provisioning for every developer and environment, and ensuring frequent, small, reversible changes with close collaboration between DBAs and developers. This approach scales to hundreds of developers and database instances without increasing DBA headcount, significantly reducing release risk and supporting uninterrupted 24/7 operations.
Runpod report: Qwen has overtaken Meta's Llama as the most-deployed self-hosted LLM (4 minute read)
Runpod's analysis of anonymized AI infrastructure logs from over 500,000 developers reveals Qwen has surpassed Llama as the most-deployed self-hosted LLM, despite Llama's higher visibility.
Synthetic data, real harm (9 minute read)
Synthetic data addresses challenges of data scarcity, fairness, and privacy in AI development by enabling dataset augmentation, reducing bias, and bypassing regulatory hurdles, but introduces risks of data pollution, model collapse, and subtle privacy breaches.
Curated deep dives, tools and trends in big data, data science and data engineering 📊
Join 590,000 readers for
one daily email