Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,318 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Explainer posts
Choosing Data Governance Tools for Enterprise Data Governance
Enterprise data governance tools address fragmented data estates in which teams struggle to locate assets, identify ownership, protect sensitive information, and maintain consistent quality across warehouses, lakes, SaaS applications, and spreadsheets. Positioned above storage and compute, these tools read metadata, schemas, and query logs to provide a shared governance layer for cataloging, lineage, classification, policy enforcement, quality monitoring, and audit reporting. The guide distinguishes standalone catalogs, point solutions, enterprise suites, platform-native tools, and open-source options while treating AI and agent governance as an increasingly important capability for models, prompts, and autonomous agents. It recommends evaluating candidates against seven criteria, comparing total cost of ownership, and planning a phased rollout that starts with highest-risk domains; a lakehouse-native approach can reduce synchronization between separate governance systems.
Anthropic Economic Index: Insights from Claude 3.7 Sonnet
Anthropic’s second Economic Index report examines how Claude.ai usage changed after Claude 3.7 Sonnet launched, using 1 million anonymized Free and Pro conversations from the following 11 days. Clio maps conversations to 17,000 tasks in the U.S. Department of Labor’s O*NET database, enabling comparisons across occupations and interaction modes, while the report also introduces a 630-category bottom-up taxonomy. Coding, education, and science usage increased modestly, and extended thinking appeared most often in technical and creative work, including computer science research, software development, multimedia art, and video game design. Augmentation remained 57% of usage, learning interactions rose from about 23% to 28%, and the report releases task- and occupation-level datasets covering thinking mode and augmentation-versus-automation patterns.
Data Mesh vs. Data Fabric: Key Differences and How the Lakehouse Resolves the Debate
Data mesh and data fabric address different constraints in distributed data architecture: mesh changes ownership and accountability, while fabric automates integration and governance. A data fabric uses active metadata, machine learning, centralized policy enforcement, and virtualized access to discover, govern, and connect data across heterogeneous environments with less data movement. A data mesh assigns domain teams responsibility for data products, quality, reliability, and lifecycle management, supported by self-serve infrastructure and federated computational governance. The article presents a lakehouse as a substrate where domains publish products while capabilities such as Unity Catalog, Delta Sharing, and Lakehouse Federation provide metadata, governance, and sharing. Its conclusion is that the approaches are complementary: organizations should identify whether organizational bottlenecks or technical fragmentation is the dominant constraint, then consider a hybrid.
Granite 4.2 LLMs: How They're Built
Granite 4.2 is IBM’s first family of dense, decoder-only reasoning language models, offered in 3B, 8B, and 30B sizes. The models use a shared design built around Grouped Query Attention, Rotary Position Embedding, SwiGLU, RMSNorm, bfloat16 precision, and separate input/output embeddings; each has a 131,072-token sequence length. Pre-training starts from scratch on approximately 15 trillion tokens across five phases, with the final phase extending the context window to 512K tokens. Supervised fine-tuning uses about 7.2 million samples spanning agentic and non-agentic data, followed by multi-stage reinforcement learning; the 8B and 30B models also receive agentic RL in sandboxed environments for tool use, code execution, terminal control, and web search. All models support thinking, non-thinking, and low-effort thinking modes, native tool calling, and Apache 2.0 licensing.
Read your writes: WAIT FOR in PostgreSQL 19
PostgreSQL 19 introduces the top-level SQL command WAIT FOR, addressing stale reads that can occur when an application writes to a primary and immediately reads from an asynchronously replicated standby. After the write, the client or pooler obtains an LSN with pg_current_wal_insert_lsn() and sends it to the reading session, where WAIT FOR blocks until the requested WAL position reaches the selected stage. The default standby_replay mode makes the change visible, while standby_write, standby_flush, primary_flush, TIMEOUT, and NO_THROW provide other durability and error-handling choices. The command waits without holding a snapshot, avoiding a replay self-deadlock, and exposes related wait events in pg_stat_activity. The feature preserves asynchronous writes by making only reads that require read-your-writes consistency wait, though timeline changes after promotion require caution.
ClickGap: Autonomous QA for ClickHouse
ClickGap addresses defects that survive ClickHouse’s extensive CI, human review, and in-house automated review, including untested behavior, silent resource waste, and performance regressions. The autonomous QA daemon examines eligible merged pull requests against verified builds, uses separate bug and coverage analysts, and requires hypotheses to become executed tests. An adversarial reviewer and ten evidence gates check consequences, source citations, complete-file review, reproducibility, and other conditions before a report can be filed. Five months after launch, ClickGap had filed roughly 500 issues and opened around 200 coverage or fix pull requests; more than half of the issues were closed, with over 200 linked to a fix PR. The system’s central design goal is to make reports trustworthy rather than merely prolific.
Ideas Worth a Longer Conversation: The JetBrains Research Podcast
The JetBrains Research Podcast investigates foundational software development and computer science questions through discussions with industry researchers. In team psychology, Cat Hicks demonstrates that collaborative culture and organizational belonging reduce developer anxiety around automated tooling while curbing the risks of overproduction pressure. Historical analysis by Tomáš Petříček shows that programming spans five competing cultures rather than pure specification implementation, explaining why automated code generation historically encounters limits. Regarding artificial intelligence evaluation, Ibragim Badertdinov details how SWE-rebench isolates model capability through dataset decontamination, leveraging the strict verifiability of software test execution for training feedback. Additionally, conversations with Alexander Kulikov and Anna Kogan examine how foundational mathematical understanding aids AI oversight and address adoption hurdles for open-source computer vision infrastructure.
Inside LinkedIn's cognitive memory agent for agentic personalization
LinkedIn built a cognitive memory agent to deliver personalized experiences across its recruiter workflows and hiring assistants. Interactions between recruiters and agents often reveal recurring preferences, such as candidate criteria, role adjustments, and task habits. To preserve and manage this state throughout the entire lifecycle, the system organizes user data into a multi-tiered memory architecture. This structure comprises conversational, semantic, episodic, and procedural memory tiers that track everything from ongoing sessions to cross-session behaviors and workflow methods. LinkedIn continues to research memory abstractions, dynamic session compaction, virtual file system storage layers, and robust evaluation approaches for attribution across complex multi-source application agents.
Open Table Formats Explained: Iceberg vs. Delta vs. Hudi
Open table formats add metadata layers over Parquet or ORC files in object storage, enabling ACID transactions, schema evolution, time travel, and database-like consistency for data lakes. Apache Iceberg uses manifests and manifest lists in a metadata tree, supports partition evolution without rewriting existing files, and creates immutable snapshots for auditing, rollback, and reproducible queries. Delta records atomic writes in an ordered transaction log with checkpoints and is closely associated with Spark, while Hudi uses record-level indexes for frequent updates, change-data-capture, and near-real-time ingestion. All three share core capabilities but differ in partition evolution, update and delete strategies, and multi-engine support; Parquet and ORC remain file formats rather than table formats. The overview recommends scheduled compaction, metadata maintenance, health monitoring, and a production-volume proof of concept when selecting a format.
Red Hat OpenShift autoscaling with Cluster Autoscaler
Red Hat OpenShift supports compute scaling using Cluster Autoscaler integrated with the OpenShift machine API. The mechanism relies on paired ClusterAutoscaler and MachineAutoscaler custom resources to manage cluster-wide limits and per-MachineSet replica boundaries. Scaling decisions evaluate pending pods against node allocatable capacity and hypothetical node capacity annotations while respecting expander strategies like Random, LeastWaste, or Priority. Cluster Autoscaler checks for unnecessary nodes every 10 seconds, scaling down when utilization falls below configured thresholds and workloads can safely migrate. To mitigate provisioning delays, clusters can adopt overprovisioning via low-priority pause containers or use APIs like ProvisioningRequest and CapacityBuffer for predictive scaling.
Agent Observability: Monitoring Decisions, Not Requests
Agent observability captures the sequence of decisions an agent makes between model calls, not just request-level metrics, and is distinct from monitoring (health) and evaluation (quality). Unlike deterministic database systems, an agent can succeed at every step yet fail overall—for example, looping forever on a failed fix while spans report success. The primary artifact is a trace, a parent-child tree of spans covering agent invocations, model calls, tool executions, and memory reads and writes. OpenTelemetry GenAI conventions define span types like create_agent and execute_tool, but the standards are still in development and change frequently; vendor support includes Datadog, Honeycomb, and frameworks like LangChain and CrewAI. A reasoning trace layer on top of operational telemetry explains why an agent chose that path; in multi-agent systems the trace must span the full coordination chain, not one agent’s output.
Whatever You Are Building, Auth0 Has a Plan
Authentication and identity requirements vary substantially as software organizations scale from solo builders to multi-brand enterprises. Building and maintaining authentication in-house frequently consumes valuable engineering cycles and incurs ongoing costs associated with security patching and edge cases. To address these distinct development stages, Auth0 structures its platform across Free, Essentials, Professional, and Enterprise tiers with differentiated B2C and B2B pricing. Early-stage and growing teams gain access to enterprise connections, SCIM user synchronization, and multi-tenant routing through Auth0 Organizations. Larger customer deployments utilize features like multi-app Single Sign-On and passwordless logins, which have driven reported outcomes such as a 20% conversion lift and a 66% reduction in identity management time.
Your alt text passes automated checks. That doesn’t mean it’s any good.
Automated accessibility checkers reliably flag missing alt text attributes but frequently miss unhelpful descriptions like raw filenames or repetitive labels. To evaluate image description quality without generating excessive false positives, GitHub built an alt text plugin for the GitHub Accessibility Scanner. The tool combines five deterministic, zero-credential rules that evaluate strings and visual layout spacing with an opt-in vision model check for subjective context. Page context including headings and surrounding prose is extracted alongside images to guide the model using structured outputs and explicit anti-nitpick instructions. While deterministic checks catch unwritten text, the model-driven rule serves as an opt-in prompt for human review rather than an absolute verdict.
MTIA 300: Meta’s First Training Chip with Built-in NICs and Communication-Offloading Engines
MTIA 300 is Meta’s first in-house training and inference accelerator optimized for ranking and recommendation models. These workloads require frequent AllReduce, AllToAll, and AllGather operations because embedding tables can contain over 99% of model parameters, making communication a bottleneck that competes with computation on GPUs. Its package-integrated network uses two chiplets with twelve custom 800 Gbps RDMA NICs, while 16 message engines and near-memory compute handle collectives independently of the 12×6 processing-element grid. Co-designed HCCL compiles collectives into dependency-aware subgraphs for autonomous execution, with topology-aware algorithms spanning scale-up and scale-out links. In production, HCCL reaches up to 940 GB/s within a rack, and a 150-billion-parameter model across 40 accelerators completed communication 3.9 times faster than an equivalent GPU cluster; concurrent GEMMs degraded less than 0.5%.
How Databricks Uses AI to Accelerate Incident Investigation
Databricks describes AI SRE, an AI-powered debugging agent for operating hundreds of microservices across more than 1,500 Kubernetes clusters, 70+ regions, and three clouds. It addresses incident investigations by assembling context from platform health, service telemetry, changes, dependencies, and team-specific runbooks, with automatic triage followed by interactive, natural-language investigation. The platform uses layered primitives, purpose-built APIs, and a core orchestration engine; team-owned agentic runbooks encode domain procedures, while controlled access and evidence links support auditing. The post reports support for more than 150 teams, 250+ weekly active users, and over 2,000 daily investigations, with users saving several hours of debugging time.
Relational vs Non-Relational Database: Choosing the Right Data Store
Selecting between relational and non-relational databases requires matching the data store to requirements for structure, consistency, scale, and query complexity. Relational systems organize data in predefined tables, enforce schemas and keys, and provide ACID transactions, making them suited to structured, transactional workloads and complex joins. Non-relational systems support documents, key-value pairs, graphs, or wide-column structures, often using flexible schemas and schema-on-read while scaling horizontally and accepting eventual consistency for throughput and availability. The trade-offs include vertical versus horizontal scaling, SQL versus database-specific query languages, and database-enforced versus application-level integrity. The guidance recommends documenting workload needs, prototyping with realistic volumes and failure scenarios, and considering polyglot persistence when different workloads require specialized systems.
Transactional Vs Analytical Database: Choosing OLTP, OLAP, or Hybrid
Transactional and analytical databases serve different workloads: OLTP handles high-volume, real-time reads and writes with ACID guarantees, while OLAP supports complex queries over large historical datasets for reporting and business intelligence. The comparison focuses on trade-offs involving latency, concurrency, data freshness, schema design, transaction size, and storage format. Row-oriented storage and normalized schemas support precise operational updates, whereas column-oriented storage and denormalized designs improve compression, scans, and aggregations across millions of rows. The source describes transactional systems as foundational for applications such as banking, e-commerce, healthcare, and reservations, while analytical systems support dashboards, forecasting, and ad-hoc analysis. Its recommended architecture is to run both systems independently and connect them with Change Data Capture, balancing operational reliability with analytical throughput.
Giga-Scale AI and the Ethernet Evolution: How Spectrum-X Ethernet Rewrites the Rules
Generative AI training across hundreds of thousands of GPUs makes the scale-out network a first-order performance bottleneck, because synchronized collectives expose weaknesses in conventional Ethernet. Static ECMP, packet loss controls such as PFC, and slowly tuned congestion control can create stragglers, head-of-line blocking, latency spikes, and multi-tenant interference. Spectrum-X Ethernet addresses these conditions with hardware-accelerated adaptive per-packet routing, targeted ECN- and RTT-based congestion control, and a SuperNIC Plane Load Balancer that distributes traffic across independent network planes. Spectrum-X Multiplane uses shallow two-tier fat trees and host-edge optical devices to provide path diversity while scaling a two-tier design to over 128,000 endpoints. In the cited tests, Spectrum-X sustained 98% of theoretical line rate across GPU pairs, held P99 tail latency to 8–9 microseconds under 75% load, recovered from a link flap in 2.68 milliseconds, and limited bandwidth loss under 10% fabric failure to 11%.
Maximizing AI Factory Performance per Watt with NVIDIA DSX MaxLPS
Power-constrained AI factories measure efficiency by AI output per watt, because facility overhead, rack losses, and operational inefficiency reduce the power available to compute. In an illustrative 100 MW budget, 60% reaches AI load, while static rack provisioning can strand headroom that another rack could use. NVIDIA DSX MaxLPS addresses this with dynamic power allocation, workload-profile power optimization, and 45° C thermal and site design, including warm-water liquid cooling. Its Dynamic Power Software, currently in Developer Preview, models topology from utility to GPUs and reallocates unused capacity within policy-defined budgets, with optional DSX Exchange integration. For Vera Rubin NVL72, NVIDIA projects up to 40% more Rubin GPU capacity within the same power budget, while validation compares unmanaged and managed runs using throughput, latency, errors, power, utilization, and compliance.
NVIDIA BlueField-4 Powers New Scale-In Network Infrastructure for Agentic AI Factories
Agentic AI factories connect diverse users, agents, applications, data sources, and storage systems to massively accelerated compute, making dedicated DPU processing essential for line-rate networking, storage, and security. Scale-In evolves north-south access into a coordinated infrastructure domain built with BlueField-4, NVIDIA DOCA, and Spectrum-X Ethernet. BlueField-4 combines programmable control-plane processing with inline data-path engines, a 64-core Grace CPU, LPDDR5X memory, PCIe Gen6 host connectivity, and an 800 Gb/s network interface. The architecture offloads security, tenant isolation, storage protocols, provisioning, and telemetry from host CPUs; the source states that Spectrum-X storage paths can provide up to 1.45x the throughput of off-the-shelf Ethernet, while independent control and observability support more consistent operations as AI infrastructure scales.
Top topics
- Architecture830
- Performance812
- LLMs648
- Machine Learning617
- Open Source561
- AI Agents542
- AI454
- Developer Experience446
Weekly digest
The best engineering reads, once a week.