{"id":49727,"date":"2026-05-12T13:25:16","date_gmt":"2026-05-12T11:25:16","guid":{"rendered":"https:\/\/www.convotis.com\/es\/?p=49727"},"modified":"2026-05-12T10:26:55","modified_gmt":"2026-05-12T08:26:55","slug":"designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand","status":"publish","type":"post","link":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/","title":{"rendered":"Designing Data Architecture: If Ownership Isn\u2019t Defined, You\u2019re Building on Sand"},"content":{"rendered":"<p>Undefined data ownership is the most common cause of conflicting reports, fragile processing pipelines, and failed governance initiatives \u2013 an architecture that addresses this structurally looks very different from what most organizations operate today.<\/p>\n<h2><strong>The Problem Has a Name &#8211; and It\u2019s Not \u201cBad Data\u201d<\/strong><\/h2>\n<p>Data swamps, conflicting reports, fragile processing pipelines. In almost every company we support at CONVOTIS, the root cause is the same: data has no owner. Not because nobody wants responsibility \u2013 but because the architecture itself does not structurally account for ownership.<\/p>\n<p>Every organization faces three questions that must be answered before selecting the first tool:<\/p>\n<ul>\n<li><strong>Who is responsible for quality?<\/strong><br \/>\nIn practice, the answer \u201ceveryone\u201d is identical to \u201cno one.\u201d Domain-based ownership \u2013 where the producing team is responsible \u2013 sounds trivial, but requires organizational anchoring. A RACI matrix alone is not enough.<\/li>\n<li><strong>Where is it authoritatively defined what an \u201cactive customer\u201d means?<\/strong><br \/>\nUsually in a spreadsheet with three competing versions, none of which is considered official. A semantic layer in the repository solves this technically \u2013 but only if it is also clear who owns that definition.<\/li>\n<li><strong>At which processing stage is a dataset considered ready for decision-making?<\/strong><br \/>\nWithout explicit quality zones, everything ends up unfiltered in analytics tools. The result: reports that contradict each other, and discussions about which one is correct \u2013 instead of what the data is actually saying.<\/li>\n<\/ul>\n<p>An architecture that leaves these three questions unanswered shifts trust toward gut feeling.<\/p>\n<h2><strong>When Is the Transformation Worthwhile &#8211; and When Isn\u2019t It?<\/strong><\/h2>\n<p>Before diving into architecture, an honest assessment: the managed data product model is not a universal remedy.<\/p>\n<p>Fewer than five teams, fewer than twenty datasets \u2013 lightweight conventions are entirely sufficient. The overhead becomes worthwhile when dependent teams block each other, when the cost of a data outage exceeds the effort of governance, or when a GDPR access request currently takes three weeks.<\/p>\n<p>Introduced too early: complexity without value. Introduced too late: rebuilding on an unstable foundation, burdened by accumulated technical and organizational debt.<\/p>\n<h2><strong>What a Data Product Is &#8211; and Why Traditional Pipelines Fail<\/strong><\/h2>\n<p>The decisive shift is conceptual: away from the idea that data flows, toward the idea that data is delivered.<\/p>\n<p>A data product is a clearly defined, versioned, documented, and monitored unit \u2013 comparable to an interface contract between teams. It has a stable access point, a defined service level, and a responsible team. Data Mesh describes this approach as domain-driven data ownership \u2013 not a tool, not a stack, but an organizational principle with technical consequences.<\/p>\n<p>A mature data product fulfills six conditions:<\/p>\n<ul>\n<li><strong>Discoverable<\/strong> \u2013 in the data catalog, not through word of mouth or internal email chains<\/li>\n<li><strong>Documented<\/strong> \u2013 machine-readable field definitions, not buried in an abandoned wiki<\/li>\n<li><strong>Quality commitment<\/strong> \u2013 measurable SLOs, not statements like \u201cshould probably be correct\u201d<\/li>\n<li><strong>Stable access point<\/strong> \u2013 no silent schema breaks, no migration chaos<\/li>\n<li><strong>Clear ownership<\/strong> \u2013 one team, not a committee or blurred responsibilities<\/li>\n<li><strong>Automated quality validation<\/strong> \u2013 during every processing step, not afterward<\/li>\n<\/ul>\n<p>Anyone who leaves out even one of these conditions is not building data products. They are building well-intentioned tables.<\/p>\n<p>The most expensive mistakes almost always occur around condition five \u2013 not because nobody checks, but because it is unclear who must respond to an alert. In one project we took over at CONVOTIS, monitoring alerts had remained unanswered for months because no team had formal responsibility. The data kept flowing. So did the decisions.<\/p>\n<p><strong>The Three Foundations: Lineage, Semantics, Quality<\/strong><\/p>\n<p>The data product is the unit. But it stands on three layers. If one is missing, the others collapse.<\/p>\n<h2><strong>Lineage Tracking: Knowing Where a Value Comes From<\/strong><\/h2>\n<p>Without lineage, troubleshooting becomes guesswork. With it, questions that otherwise take hours can be answered in minutes: where did the error occur \u2013 in the source system, during transformation, or only at delivery?<\/p>\n<p>For getting started, table-level tracking is sufficient. OpenLineage defines the open exchange format, while Marquez provides a lightweight implementation. DataHub is the more comprehensive alternative: a complete catalog with lineage, search, and classification \u2013 requiring more operational effort, but also offering broader capabilities.<\/p>\n<p>Column-level lineage becomes mandatory as soon as GDPR compliance must be demonstrable. Anyone implementing it only after the first access request quickly realizes how much work has accumulated \u2013 and how long a legally required request suddenly takes.<\/p>\n<p><strong>Semantic Layer: One Version of the Truth, Versioned<\/strong><\/p>\n<h2>Two reports, one question, two answers \u2013 a classic symptom of missing semantic authority.<\/h2>\n<p>MetricFlow (part of dbt) stores term definitions versioned in the repository: a single, validated definition of active_customers, accessible from every analytics tool. No spreadsheets, no informal agreements, no competing versions in another department.<\/p>\n<p>The familiar bottleneck: when departments compete, the semantic layer itself becomes the conflict point. Sales and Finance define \u201crevenue\u201d differently \u2013 and both have legitimate reasons. What helps is clear metric ownership and an escalation path involving business representatives before the definition enters the repository. Tools make these conflicts visible \u2013 people must resolve them.<\/p>\n<h2><strong>Quality Monitoring in the Pipeline: Validate Early, Respond Explicitly<\/strong><\/h2>\n<p>Quality checks belong in the processing pipeline \u2013 not in the report. Anyone discovering errors only in the dashboard has already enabled poor decisions.<\/p>\n<p>A proven pattern divides the pipeline into three zones:<\/p>\n<ul>\n<li><strong>Ingress zone<\/strong> \u2013 completeness, validity, format compliance<\/li>\n<li><strong>Transformation zone<\/strong> \u2013 volume consistency, business rules, referential integrity<\/li>\n<li><strong>Delivery zone<\/strong> \u2013 deviation from the previous day, quality score, release status<\/li>\n<\/ul>\n<p>The critical factor is the response strategy when checks fail: hard stop for financial data, quarantine for high-volume data, warning labels for exploratory analytics. This decision must be explicit \u2013 it must not emerge implicitly because nobody addressed it. Great Expectations and dbt Tests implement this pattern.<\/p>\n<h2><strong>Governance: Why Access Rules and Deletability Belong in the Architecture<\/strong><\/h2>\n<p>GDPR access requests, deletion requests, audits \u2013 they all ask the same question: where is this person\u2019s data stored? Anyone who first has to search for the answer has treated governance as an afterthought.<\/p>\n<p>Four measures prevent this structurally:<\/p>\n<ul>\n<li><strong>Access policies as code<\/strong> using Open Policy Agent. Without it: manual approvals, no auditability, no reproducibility.<\/li>\n<li><strong>Sensitivity labeling at field level<\/strong> in schema metadata. Without it, the platform cannot automatically mask or block data \u2013 and therefore doesn\u2019t.<\/li>\n<li><strong>Retention periods as configuration<\/strong> in the versioned repository \u2013 otherwise email chains and manual processes take over, and deadlines are forgotten.<\/li>\n<li><strong>Deletability as a design principle<\/strong> \u2013 embedded from day one.<\/li>\n<\/ul>\n<p>Retrofitted deletability is one of the most expensive architectural problems we know. Multiple teams, multiple weeks, a single access request \u2013 because nobody can answer the question \u201cwhere is this data actually stored?\u201d<\/p>\n<h2><strong>How to Start &#8211; Without Rebuilding the Entire System<\/strong><\/h2>\n<p>The most common mistake during implementation: starting too broadly. The right starting point is focused.<\/p>\n<p><strong>Step 1:<\/strong> Identify the critical data path \u2013 where reports conflict, where teams blame each other, where an outage would have the greatest impact.<\/p>\n<p><strong>Step 2:<\/strong> For that exact path, implement lineage, integrate automated quality checks, and define response strategies.<\/p>\n<p><strong>Step 3:<\/strong> Clarify ownership explicitly \u2013 with names, escalation paths, and actual resources. Responsibility without resources and authority remains a statement of intent.<\/p>\n<p>Only once this path runs stably and the team genuinely lives ownership does scaling become worthwhile.<\/p>\n<h2><strong>The Point Where Technology Ends<\/strong><\/h2>\n<p>Anyone treating data quality as a project goal will face a new problem after go-live. The tools for stable operations exist \u2013 mature, proven, well documented. What is almost always missing is someone who feels responsible when it matters. With authority. With resources. With an escalation path that works.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Undefined data ownership is the most common cause of conflicting reports, fragile processing pipelines, and failed governance initiatives \u2013 an architecture that addresses this structurally looks very different from what most organizations operate today. The Problem Has a Name &#8211; and It\u2019s Not \u201cBad Data\u201d Data swamps, conflicting reports, fragile processing pipelines. In almost every [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":49725,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[367],"tags":[],"class_list":["post-49727","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-transformation-en"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.4 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Data architecture and clear ownership<\/title>\n<meta name=\"description\" content=\"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Data architecture and clear ownership\" \/>\n<meta property=\"og:description\" content=\"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/\" \/>\n<meta property=\"og:site_name\" content=\"CONVOTIS Iberia\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-12T11:25:16+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1090\" \/>\n\t<meta property=\"og:image:height\" content=\"670\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"elianamoldovanska\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"elianamoldovanska\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/\"},\"author\":{\"name\":\"elianamoldovanska\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#\\\/schema\\\/person\\\/43069367f8f43b4689f544f0d1e798af\"},\"headline\":\"Designing Data Architecture: If Ownership Isn\u2019t Defined, You\u2019re Building on Sand\",\"datePublished\":\"2026-05-12T11:25:16+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/\"},\"wordCount\":1236,\"publisher\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2026\\\/05\\\/Data-Architecture-Data-lake_article.png\",\"articleSection\":[\"Digital Transformation\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/\",\"url\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/\",\"name\":\"Data architecture and clear ownership\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2026\\\/05\\\/Data-Architecture-Data-lake_article.png\",\"datePublished\":\"2026-05-12T11:25:16+00:00\",\"description\":\"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/en\\\/news\\\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2026\\\/05\\\/Data-Architecture-Data-lake_article.png\",\"contentUrl\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2026\\\/05\\\/Data-Architecture-Data-lake_article.png\",\"width\":1090,\"height\":670},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#website\",\"url\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/\",\"name\":\"CONVOTIS\",\"description\":\"For Europe&#039;s digital future.\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#organization\",\"name\":\"CONVOTIS\",\"url\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2025\\\/08\\\/Convotis_blue_cmyk300dpi-scaled.png\",\"contentUrl\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/wp-content\\\/uploads\\\/sites\\\/3\\\/2025\\\/08\\\/Convotis_blue_cmyk300dpi-scaled.png\",\"width\":2560,\"height\":411,\"caption\":\"CONVOTIS\"},\"image\":{\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/convotis-gmbh\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.convotis.com\\\/es\\\/#\\\/schema\\\/person\\\/43069367f8f43b4689f544f0d1e798af\",\"name\":\"elianamoldovanska\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g\",\"caption\":\"elianamoldovanska\"},\"sameAs\":[\"https:\\\/\\\/www.convotis.com\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Data architecture and clear ownership","description":"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/","og_locale":"en_US","og_type":"article","og_title":"Data architecture and clear ownership","og_description":"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.","og_url":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/","og_site_name":"CONVOTIS Iberia","article_published_time":"2026-05-12T11:25:16+00:00","og_image":[{"width":1090,"height":670,"url":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png","type":"image\/png"}],"author":"elianamoldovanska","twitter_card":"summary_large_image","twitter_misc":{"Written by":"elianamoldovanska","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/#article","isPartOf":{"@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/"},"author":{"name":"elianamoldovanska","@id":"https:\/\/www.convotis.com\/es\/#\/schema\/person\/43069367f8f43b4689f544f0d1e798af"},"headline":"Designing Data Architecture: If Ownership Isn\u2019t Defined, You\u2019re Building on Sand","datePublished":"2026-05-12T11:25:16+00:00","mainEntityOfPage":{"@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/"},"wordCount":1236,"publisher":{"@id":"https:\/\/www.convotis.com\/es\/#organization"},"image":{"@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/#primaryimage"},"thumbnailUrl":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png","articleSection":["Digital Transformation"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/","url":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/","name":"Data architecture and clear ownership","isPartOf":{"@id":"https:\/\/www.convotis.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/#primaryimage"},"image":{"@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/#primaryimage"},"thumbnailUrl":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png","datePublished":"2026-05-12T11:25:16+00:00","description":"Find out why a lack of data ownership leads to governance failures, conflicting reports, and unmanaged data lakes.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.convotis.com\/es\/en\/news\/designing-data-architecture-if-ownership-isnt-defined-youre-building-on-sand\/#primaryimage","url":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png","contentUrl":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2026\/05\/Data-Architecture-Data-lake_article.png","width":1090,"height":670},{"@type":"WebSite","@id":"https:\/\/www.convotis.com\/es\/#website","url":"https:\/\/www.convotis.com\/es\/","name":"CONVOTIS","description":"For Europe&#039;s digital future.","publisher":{"@id":"https:\/\/www.convotis.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.convotis.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.convotis.com\/es\/#organization","name":"CONVOTIS","url":"https:\/\/www.convotis.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.convotis.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2025\/08\/Convotis_blue_cmyk300dpi-scaled.png","contentUrl":"https:\/\/www.convotis.com\/es\/wp-content\/uploads\/sites\/3\/2025\/08\/Convotis_blue_cmyk300dpi-scaled.png","width":2560,"height":411,"caption":"CONVOTIS"},"image":{"@id":"https:\/\/www.convotis.com\/es\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/convotis-gmbh\/"]},{"@type":"Person","@id":"https:\/\/www.convotis.com\/es\/#\/schema\/person\/43069367f8f43b4689f544f0d1e798af","name":"elianamoldovanska","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/dcc0c0bd213565a66bfb488266616c3e473f54a3fdd5c34226d23758988c7924?s=96&d=mm&r=g","caption":"elianamoldovanska"},"sameAs":["https:\/\/www.convotis.com\/"]}]}},"_links":{"self":[{"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/posts\/49727","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/comments?post=49727"}],"version-history":[{"count":1,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/posts\/49727\/revisions"}],"predecessor-version":[{"id":49728,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/posts\/49727\/revisions\/49728"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/media\/49725"}],"wp:attachment":[{"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/media?parent=49727"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/categories?post=49727"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.convotis.com\/es\/wp-json\/wp\/v2\/tags?post=49727"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}