<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Athena on Sakura Sky: Cloud, Data, Security</title><link>https://www.sakurasky.com/tags/athena/</link><description>Recent content in Athena on Sakura Sky: Cloud, Data, Security</description><generator>Hugo</generator><language>en-US</language><copyright>Sakura Sky</copyright><lastBuildDate>Mon, 29 Jun 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://www.sakurasky.com/tags/athena/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Costs: Are You a Victim of Your Own Success?</title><link>https://www.sakurasky.com/blog/data-costs-are-you-a-victim-of-your-own-success/</link><pubDate>Mon, 29 Jun 2026 00:00:00 -0400</pubDate><guid>https://www.sakurasky.com/blog/data-costs-are-you-a-victim-of-your-own-success/</guid><description>&lt;p&gt;Even in an era of AI and automation, the most valuable asset we have is judgment. We talk often about saving money in the cloud, but what does that actually mean in practice? This post is about small architectural decisions that compound cost at scale, and the structural fix when they do. If you have any pipelines running today against raw object storage on a fixed cadence, there is a good chance one of them is in here.&lt;/p&gt;</description></item></channel></rss>