# semantic-layer A semantic layer is an abstraction or architecture layer that maps technical data assets to business terms, metrics, dimensions, and relationships, providing consistent definitions for analytics tools and AI systems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Data Engineering Weekly #286 DevFeed: [Data Engineering Weekly #286]() Original publisher: [Read original article]() Author: Ananth Packkildurai Published: 2026-09-07T00:18:06Z Content type: article Language: en Sources: [Data Engineering Weekly]() Topics: [data-engineering](), [AI, ML & Data Engineering](), [agent observability](), [Large Language Model](), [data-modeling](), [Monitoring](), [Scalability](), [semantic-layer](), [parquet]() Tags: [ai](), [ai-agents](), [data-engineering](), [data-modeling](), [llm](), [monitoring](), [newsletter](), [observability](), [parquet](), [scalability](), [semantic-layer](), [weekly]() ### AI overview Data Engineering Weekly #286 is a curated newsletter covering data platform fundamentals, mathematics for machine learning, agentic machine learning at Instacart, Netflix's lifecycle for LLM-as-a-Judge systems, semantic layers and data modeling for AI analytics, and Apache Pinot scalability. ### Source excerpt The Weekly Data Engineering Newsletter ## Beyond the Dashboard: Accelerating Real-Time Intelligence in the Age of AI DevFeed: [Beyond the Dashboard: Accelerating Real-Time Intelligence in the Age of AI]() Original publisher: [Read original article]() Author: Kostiantyn Okhrimenko Published: 2026-08-27T11:15:58Z Content type: article Language: en Sources: [Booking.com Development - Medium]() Topics: [semantic-layer](), [genai](), [analytics stack](), [Large Language Model](), [Artificial Intelligence](), [data](), [dashboards](), [Query (disambiguation)]() Tags: [agent](), [ai](), [ai-tools](), [analytics-stack](), [bi-tools](), [dashboards](), [data](), [genai](), [real-time](), [self-service](), [self-serving-analytics](), [semantic-layer](), [sql]() ### AI overview The article examines how GenAI-driven natural-language interfaces can help stakeholders obtain trusted data answers without repeatedly interrupting data and engineering teams. It argues that a robust semantic layer is necessary to make self-service analytics reliable and precise. ### Source excerpt When an urgent request for a report or dashboard arrives, often just before an executive meeting, data and engineering teams must drop planned work to respond. One request may be reasonable, but repeated interruptions come at a cost: important work, such as scaling infrastructure, improving reliability, models optimization, gets pushed back, while quick, one-off dashboards become more technical debt to maintain. For managers and other decision-makers, the need is real: they require reliable data to make decisions quickly. But getting an answer often depends on someone who knows SQL, understands the data structure, and has time to help. When those people are already busy, the question waits, even when the answer is sitting in the data warehouse. By the time the report is ready, the decision window may have passed. This is not just a prioritization issue. We need a better way for people to get trusted answers quickly without constantly pulling teams away from building and improving the data platform. All of the above can be illustrated by the image: Image 1: Typical reporting circleWhat we will talk about The explosion of GenAI over the last few years has shifted the focus for the modern analytics stack. We are evolving beyond traditional Data Democratization, which often gave teams access to complex pre-AI tools without clear governance, toward natural language data interaction: asking questions in plain English -- Talk to your data concept. In the traditional stack, the "interface" to data was either a dashboard or a SQL editor. This created a high barrier to entry that caused the friction. By properly architecting and utilizing GenAI-driven tools, we can finally bridge the gap between intent and insight. Talk to your data is a self-serve ecosystem where any stakeholder can bypass the traditional ticketing queue and, instead of waiting for an engineer to interpret a requirement and translate it into a query, the user engages with a specialised agent. The challenge, h ## Building an Operational Ontology: An E-Commerce Walkthrough DevFeed: [Building an Operational Ontology: An E-Commerce Walkthrough]() Original publisher: [Read original article]() Author: Togo YAMANAKA Published: 2026-08-26T14:29:30Z Content type: tutorial Language: en Sources: [Data Engineering Weekly]() Topics: [semantic-layer](), [SQL](), [TypeScript](), [Open Source](), [Databases]() Tags: [customer](), [data-pipeline](), [implementation](), [integration](), [open-source](), [semantic-layer](), [sql](), [typescript]() ### AI overview A walkthrough builds an operational ontology over integrated e-commerce order data from two systems with different schemas and status encodings. It models customers, orders, products, and relationships, then introduces named actions, business rules, and write-back to systems of record. ### Source excerpt The write side of the ontology conversation: named actions, business rules, and write-back to the systems of record -- a pattern already running at enterprise scale. ## Data Engineering Weekly #282 DevFeed: [Data Engineering Weekly #282]() Original publisher: [Read original article]() Author: Ananth Packkildurai Published: 2026-08-10T01:21:26Z Content type: article Language: en Sources: [Data Engineering Weekly]() Topics: [data-engineering](), [data-platforms](), [data observability](), [Graphs](), [semantic-layer](), [Large Language Model](), [Apache Iceberg](), [gRPC](), [Concurrency](), [Caching](), [Optimization](), [Streaming]() Tags: [caching](), [chaos](), [concurrency](), [data](), [data-engineering](), [data-platforms](), [data-quality](), [knowledge-graphs](), [llms](), [newsletter](), [observability](), [pipelines](), [semantic-layer](), [streaming]() ### AI overview Data Engineering Weekly #282 is a newsletter covering data platform fundamentals, semantic layers, ontology-backed knowledge graphs, converged databases, AI modernization, and Netflix's real-time distributed graph query architecture. It highlights composable architectures, data quality and observability, evolving schemas supported by LLM-assisted extraction, Iceberg full-text search, and optimization techniques including concurrency control, streaming filters, and caching. ### Source excerpt The Weekly Data Engineering Newsletter ## Institutional knowledge doesn't scale: Building an agentic data analyst DevFeed: [Institutional knowledge doesn't scale: Building an agentic data analyst]() Original publisher: [Read original article]() Author: Navo Das Published: 2026-08-03T10:45:52Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [data](), [semantic-layer](), [Large Language Model](), [text2sql](), [SQL](), [Databases](), [metric-standardization]() Tags: [agentic](), [analytics](), [building](), [data](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [llm](), [outage](), [post-mortem](), [semantic-layer](), [slack-incident](), [sql](), [tool]() ### AI overview The article explains why dashboard-based self-service analytics and direct LLM access to a data warehouse leave important gaps. It describes building an agentic data analyst, called the "data brain," to distribute institutional data knowledge and help employees ask questions while addressing issues such as canonical joins, filters, metrics, and judgment required to produce correct SQL. ### Source excerpt Institutional knowledge was always the bottleneck. Here's how we built an agentic data analyst to distribute it more efficiently -- and what happened when we let the whole company ask it questions. ## Dispatches from O'Reilly: The best risk mitigation strategy in data? A single source of truth DevFeed: [Dispatches from O'Reilly: The best risk mitigation strategy in data? A single source of truth]() Original publisher: [Read original article]() Author: Jeremy Arendt Published: 2026-07-31T14:08:31Z Content type: article Language: en Sources: [Stack Overflow Blog]() Topics: [semantic-layer](), [data](), [Authorization](), [dashboards](), [Artificial Intelligence]() Tags: [analytics](), [applications](), [article](), [buiilding-software](), [data](), [oreilly](), [se-stackoverflow](), [se-tech](), [semantic-layer]() ### AI overview The article presents a semantic layer as a practical risk-mitigation strategy for data operations. It describes how inconsistent metrics, fragmented governance and access controls, and poorly managed changes can create business risk, and argues that a single source of truth can reduce these problems. ### Source excerpt Your semantic layer is a risk mitigation strategy. Not risk in the abstract, compliance-framework sense, but the practical, operational risk that quietly drains organizations every day. ## Research: How we cut AI costs by 80% DevFeed: [Research: How we cut AI costs by 80%]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-30T11:24:23Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Artificial Intelligence](), [context window](), [MCP](), [semantic-layer](), [Claude](), [data](), [sdlc](), [GitHub](), [Caching]() Tags: [agents](), [ai](), [claude](), [context-window](), [cost](), [data](), [experiment](), [github](), [mcp](), [reasoning](), [sdlc](), [semantic-layer](), [tokens]() ### AI overview This research article examines rising AI costs caused by messy, repeatedly assembled context for agent queries. An experiment using thousands of production queries and a test set of 1000 commonly asked SDLC queries found that structured context was 80% cheaper than unstructured context. The proposed approach pre-relates context and uses a semantic layer to reduce data hops, reasoning, and token consumption. ### Source excerpt We ran thousands of AI queries on unstructured and structured context and measured the cost. Structured context was 80% cheaper than unstructured. ## Dashboards aren't (quite) dead DevFeed: [Dashboards aren't (quite) dead]() Original publisher: [Read original article]() Author: Jack Colsey Published: 2026-07-29T16:24:00Z Content type: opinion Language: en Sources: [The incident.io Blog]() Topics: [dashboards](), [Large Language Model](), [semantic-layer](), [metric-standardization](), [data]() Tags: [analytics](), [dashboards](), [data](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [llms](), [outage](), [post-mortem](), [semantic-layer](), [slack-incident]() ### AI overview The article argues that dashboards still matter even as LLMs make flexible, self-serve data analysis increasingly accessible. Semantic layers and reliable interfaces can help humans and LLMs calculate metrics consistently, but dashboards provide a curated, trusted view that keeps the business aligned on which interpretation of the data matters. ### Source excerpt How they still matter as the curated, trusted layer that keeps both humans and LLMs telling the same story from the same data. ## Data Engineering Weekly #279 DevFeed: [Data Engineering Weekly #279]() Original publisher: [Read original article]() Author: Ananth Packkildurai Published: 2026-07-20T04:07:20Z Content type: article Language: en Sources: [Data Engineering Weekly]() Topics: [data-engineering](), [Data Quality](), [semantic-layer](), [Kafka](), [observability](), [knowledge-engineering](), [Embeddings](), [Databases](), [Amazon EKS](), [Amazon EC2](), [Availability]() Tags: [availability](), [data-engineering](), [data-quality](), [database](), [embeddings](), [engineering](), [kafka](), [knowledge-engineering](), [observability](), [semantic-layer]() ### AI overview Data Engineering Weekly #279 is a newsletter covering data platform fundamentals, data management for generative AI, semantic-layer portability, knowledge-base construction with Postgres and embeddings, Kafka migration, and Apache Pinot high availability. The supplied text includes sponsored material and ends mid-item. ### Source excerpt The Weekly Data Engineering Newsletter ## Data Engineering Weekly #275 DevFeed: [Data Engineering Weekly #275]() Original publisher: [Read original article]() Author: Ananth Packkildurai Published: 2026-06-22T04:02:10Z Content type: article Language: en Sources: [Data Engineering Weekly]() Topics: [data-engineering](), [semantic-layer](), [Data Quality](), [observability](), [Model Context Protocol](), [Python](), [SQL](), [YAML]() Tags: [data-engineering](), [data-quality](), [mcp](), [metrics](), [observability](), [pipelines](), [python](), [semantic-layer](), [sql](), [yaml]() ### AI overview Data Engineering Weekly #275 is a newsletter issue covering data platform fundamentals, semantic layers, metric governance, idempotent pipeline design, and AI modernization. It highlights how shared business definitions, data quality, observability, and retry-safe writes support reliable analytics and AI workflows. ### Source excerpt The Weekly Data Engineering Newsletter ## Get reliable answers to business questions with Bits Data Analysis DevFeed: [Get reliable answers to business questions with Bits Data Analysis]() Original publisher: [Read original article]() Author: Jonathan Morin; Jonathan Parisot; Harel Shein Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Data analysis](), [data observability](), [semantic-layer](), [SIEM, Security, Observability](), [Model Context Protocol](), [ai-coding]() Tags: [ai](), [ai-coding](), [analytics](), [bits-ai](), [data-analytics](), [data-engineering](), [data-observability](), [digital-experience-monitoring](), [mcp](), [observability](), [root-cause-analysis](), [semantic-layer]() ### AI overview Bits Data Analysis, now in Preview, helps teams answer business questions with governed context from their data stack and Datadog telemetry. It uses metric definitions, lineage, freshness, quality signals, application telemetry, and source code to select appropriate data and provide confidence indicators with links to the definitions and tables used. ### Source excerpt Learn how Bits Data Analysis answers business questions using governed data context from Datadog.