<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title><![CDATA[Crag Meshblend]]></title>
  <link>https://crag-meshblend.com/</link>
  <description><![CDATA[Crag Meshblend unifies fragmented enterprise data into a single queryable mesh. Tokyo-based software platform for manufacturing, retail, and financial services teams in Japan.]]></description>
  <language>en</language>
  <atom:link href="https://crag-meshblend.com/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title><![CDATA[What is a data mesh and why does it matter in Japan]]></title>
    <link>https://crag-meshblend.com/notes/what-is-data-mesh-japan.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/what-is-data-mesh-japan.html</guid>
    <description><![CDATA[The term 'data mesh' has been circulating in Japanese IT departments since around 2022, but the explanations tend to be either too abstract or too tied to the specific tooling of a particular vendor. This article explains the concept plainly, describes where it fits in a typical Japanese enterprise data environment, and points out where it does not fit.]]></description>
    <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[How to document APPI compliance from your data platform]]></title>
    <link>https://crag-meshblend.com/notes/appi-compliance-data-platform.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/appi-compliance-data-platform.html</guid>
    <description><![CDATA[Japan's Act on the Protection of Personal Information was significantly revised in 2022, and the amendments that came into force that year added new obligations around data lineage, breach notification, and third-party data transfers. For companies that handle personal data across multiple systems, demonstrating compliance requires more than a privacy policy. It requires documented evidence of where personal data lives, who can access it, and what happens to it.]]></description>
    <pubDate>Fri, 03 Apr 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Running a data mesh on-premise in a Japanese data centre]]></title>
    <link>https://crag-meshblend.com/notes/on-premise-data-mesh-japan.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/on-premise-data-mesh-japan.html</guid>
    <description><![CDATA[Cloud-managed data platforms are the default assumption in most vendor documentation, but a significant number of Japanese enterprises. Particularly in financial services and manufacturing. Operate under security policies that require data to remain in their own facilities. Deploying a data mesh on-premise introduces a set of constraints that are worth understanding before you start.]]></description>
    <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Data integration challenges in Japanese manufacturing]]></title>
    <link>https://crag-meshblend.com/notes/data-integration-manufacturing-japan.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/data-integration-manufacturing-japan.html</guid>
    <description><![CDATA[Japanese manufacturing environments typically run a mix of production control systems, ERP instances, quality management databases, and supplier data feeds that were built at different times by different vendors and were never designed to share data. The result is a set of silos that each contain accurate data about their own domain, but cannot answer questions that cross domain boundaries.]]></description>
    <pubDate>Tue, 27 Jan 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Querying across databases without a data warehouse]]></title>
    <link>https://crag-meshblend.com/notes/sql-virtual-schema-no-warehouse.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/sql-virtual-schema-no-warehouse.html</guid>
    <description><![CDATA[The standard advice for organisations that need to query across multiple databases is to build a data warehouse: copy everything into one place, transform it into a common schema, and query from there. This works, but it introduces a copy of your data that needs to be maintained, a transformation pipeline that breaks when source schemas change, and a latency between when data is written and when it is queryable. Virtual schemas are an alternative that avoids all three of those problems, with some trade-offs.]]></description>
    <pubDate>Fri, 14 Nov 2025 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Data governance for a team that does not have a data team]]></title>
    <link>https://crag-meshblend.com/notes/data-governance-small-team-japan.html</link>
    <guid isPermaLink="true">https://crag-meshblend.com/notes/data-governance-small-team-japan.html</guid>
    <description><![CDATA[Data governance tends to be discussed as if it requires a dedicated team of data stewards, a governance committee, and a multi-year programme. For most mid-size Japanese companies, that is not realistic. This article describes the minimum viable governance setup that a small IT team can implement and maintain without it becoming a full-time job.]]></description>
    <pubDate>Mon, 08 Sep 2025 00:00:00 GMT</pubDate>
  </item>
</channel>
</rss>
