<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vortex on Medium]]></title>
        <description><![CDATA[Stories by Vortex on Medium]]></description>
        <link>https://medium.com/@VortexCloud?source=rss-16c38efb6a6c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*daWjs0j56lbQSbYJ6EWTGQ.png</url>
            <title>Stories by Vortex on Medium</title>
            <link>https://medium.com/@VortexCloud?source=rss-16c38efb6a6c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:37:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@VortexCloud/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Napsali o nás v AI Cruch: Proč je Článek 50 AI Actu šancí, jak se zbavit technického dluhu?]]></title>
            <link>https://medium.com/@VortexCloud/napsali-o-n%C3%A1s-v-ai-cruch-pro%C4%8D-je-%C4%8Dl%C3%A1nek-50-ai-actu-%C5%A1anc%C3%AD-jak-se-zbavit-technick%C3%A9ho-dluhu-d8ac33cc8d85?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8ac33cc8d85</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[eu-ai-act]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-governance]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 08:19:55 GMT</pubDate>
            <atom:updated>2026-09-04T08:19:55.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ukJLCFUp8jZdQ2q5.png" /><figcaption>Michaela Kuralová, Marketingová Manažerka ve firmě <a href="http://www.vortexcloud.io/">VotexCloud.io</a></figcaption></figure><h3>Proč je Článek 50 AI Actu šancí, jak se zbavit technického dluhu? Byli jsme vidět v AI Crunch</h3><p>Zákazníci neodcházejí proto, že mluví s botem — odcházejí, když nedostanou správnou odpověď. Nástup Článku 50 evropského Aktu o AI zavádí povinnou transparentnost pro AI agenty a staví toto téma z pohledu rizik přímo vedle GDPR.</p><p>Ve <strong>Vortex Cloud</strong> se ale na novou regulaci nedíváme jako na překážku, ale jako na ideální příležitost udělat pořádek v architektuře.</p><p>Prestižní technologický magazín <a href="https://aicrunch.cz/clanek-50-ai-actu-v-produkci-jak-postavit-transparentni-architekturu-bez-bezpecnostniho-dluhu"><strong>AI Crunch</strong></a> otiskl autorský článek naší kolegyně <strong>Michaely Kuralové</strong>, ve kterém rozebírá, jak postavit transparentní a bezpečnou AI architekturu v produkci — bez bezpečnostního dluhu a zbytečně propáleného rozpočtu.</p><h3>O čem se v článku dočtete?</h3><ul><li><strong>Proč AI governance nepočká:</strong> Jak se vyhnout astronomickým fakturám za API a riziku prompt injection útoků (jak trefně připomíná náš Head of Sales Pavel Klemš).</li><li><strong>Smart Model Routing v praxi:</strong> Jak díky správnému směrování dotazů ušetřit 60–70 % provozních nákladů, aniž by utrpěla rychlost (pohled našeho DevOps Engineeru Michala Zindulky).</li><li><strong>Reálné příklady na Google Cloud:</strong> Jak transparentnost a datovou izolaci řeší např. <strong>GymBeam</strong> u virtuální zkušební kabinky nebo <strong>Dine4Fit (Kalorické tabulky)</strong> u rozpoznávání jídla z fotek.</li></ul><h3>Proč si článek přečíst?</h3><p>Pokud ve firmě vyvíjíte nebo nasazujete AI agenty a nechcete spoléhat na ad hoc skripty, získáte konkrétní návod ve 3 krocích, jak vaši architekturu připravit na regulaci i reálnou zátěž.</p><p><a href="https://aicrunch.cz/clanek-50-ai-actu-v-produkci-jak-postavit-transparentni-architekturu-bez-bezpecnostniho-dluhu%C2%A8">👉 <strong>Přečtěte si celý článek na AI Crunch</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8ac33cc8d85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Všichni mluví o AI modelech. Ale kdo je skutečně dostal do produkce? ️]]></title>
            <link>https://medium.com/vortex-cloud/v%C5%A1ichni-mluv%C3%AD-o-ai-modelech-ale-kdo-je-skute%C4%8Dn%C4%9B-dostal-do-produkce-%EF%B8%8F-9e2af8210a60?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e2af8210a60</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[aritificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Wed, 21 Jan 2026 14:27:07 GMT</pubDate>
            <atom:updated>2026-01-21T14:30:42.485Z</atom:updated>
            <content:encoded><![CDATA[<h3>Konec AI hypu: Proč je „integrační propast“ největší brzdou vaší firmy (a jak ji přeskočit)</h3><p><strong>Přístup k AI modelům už není konkurenční výhoda. Je to komodita. Skutečná válka se dnes nevede o to, kdo má lepší model, ale kdo ho dokáže dostat z testovacího prostředí do “krvavého” oběhu firmy.</strong></p><p>Je to scénář, který se opakuje v zasedačkách po celém světě. CTO nadšeně ukazuje demo, kde chatbot napíše báseň nebo shrne e-mail. CEO tleská. O šest měsíců později se ale ptá: <em>“Proč to ještě neběží v naší aplikaci a nezvyšuje to tržby?”</em></p><p>Vítejte v tzv. <strong>Integration Gap</strong> (Integrační propasti).</p><p>V nejnovější epizodě podcastu <strong>Data Talk (#166)</strong> se Jiří Vicherek ponořil do tohoto problému se <strong>Samuelem Kožuchem</strong>, Data &amp; AI Team Leadem ve Vortex Cloud. A závěr je jasný: Éra “lepení AI nástrojů zvenčí” končí. Nastupuje éra “Baked-in Intelligence”.</p><p><a href="https://www.buzzsprout.com/2034779/episodes/18416927"><strong>[Poslechnout si epizodu]</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*D37Dhfdjvec_v_sFlGJUSA.jpeg" /></figure><h3>Problém: AI jako cizí těleso</h3><p>Většina firem se snaží AI naroubovat na své systémy jako externí končetinu. To přináší latenci, bezpečnostní rizika a integrační noční můry. Samuel Kožuch v podcastu vysvětluje, že budoucnost neleží v externích nástrojích, ale v infrastruktuře, která má inteligenci už v sobě — doslova “zapečenou”.</p><p>Google Cloud tento posun vede změnou paradigmatu. Už neposkytuje jen “výpočetní výkon”, ale “inteligentní výkon”.</p><h3>Řešení: Gemini CLI jako expertní co-pilot</h3><p>Jedním z nejsilnějších momentů rozhovoru je pasáž o <strong>Gemini CLI</strong>. Pokud si myslíte, že Gemini je jen další chatbot, Samuel vás vyvede z omylu.</p><p>V rukou zkušeného inženýra se Gemini CLI mění v expertního co-pilota pro kritické operace. Představte si rozsáhlé migrace IT infrastruktury. Dříve to byl “manuální maraton” — týdny mravenčí práce, skriptování a stresu z lidské chyby.</p><p>Dnes? S nástroji integrovanými přímo v cloudu se tento proces stává automatizovanou, kontrolovanou a hlavně bezpečnou rutinou. AI zde nepíše básně; AI zde chrání integritu vašich dat při přesunu petabytů informací.</p><blockquote>“Nejde o to nahradit inženýry, ale dát jim do ruky nástroj, který z rizikové operace udělá standardní proceduru.”</blockquote><h3>Důkaz místo slibů: 4 české firmy, které to dokázaly</h3><p>Teorie je hezká, ale v Data Talku jde vždy o praxi. Samuel v epizodě odhaluje, jak konkrétní hráči na trhu tuto technologii už dnes využívají v produkci:</p><ul><li><strong>🥗 Dine4Fit (Kalorické Tabulky):</strong> Zde AI nehraje roli zákaznické podpory. Multimodální modely Gemini analyzují fotografie jídla od uživatelů a v reálném čase identifikují složení talíře. Z fotky rovnou do databáze nutričních hodnot.</li><li><strong>🏋️ GymBeam:</strong> E-commerce gigant se nebál nasadit autonomní AI agenty přímo do produkčního prostředí. Výsledek? Škálovatelnost operací, o které se konkurenci jen zdá.</li><li><strong>🚴 Rouvy:</strong> Pro platformu, která simuluje reálnou cyklistiku, jsou data vším. Pokročilá analytika zde pomáhá pochopit chování uživatelů do hloubky, která byla před nástupem AI nemyslitelná.</li><li><strong>🛡️ Tatum:</strong> Ve světě blockchainu je bezpečnost na prvním místě. AI zde slouží jako první, neúnavná linie obrany při detekci podvodů a anomálií.</li></ul><h3>Poslechněte si “How-to”</h3><p>Rozdíl mezi úspěchem a selháním v AI projektech je často jen v pochopení toho, <em>jak</em> věci propojit. Pokud chcete slyšet technické detaily, strategické uvažování a upřímný pohled na to, co funguje a co ne, pusťte si celý rozhovor.</p><p>🎧 <strong>Data Talk Ep. 166: Samuel Kožuch o Google Cloud &amp; AI</strong> <br><a href="https://www.buzzsprout.com/2034779/episodes/18416927"><strong>[Poslechnout si epizodu]</strong></a></p><p><em>Tento článek vychází z podcastu Data Talk, který moderuje Jiří Vicherek. Pro více insights ze světa dat a AI sledujte Data Talk a Vortex na LinkedIn.</em></p><p>#DataTalk #GoogleCloud #AIadoption #DataEngineering #VortexCloud #TechPodcast</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e2af8210a60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/v%C5%A1ichni-mluv%C3%AD-o-ai-modelech-ale-kdo-je-skute%C4%8Dn%C4%9B-dostal-do-produkce-%EF%B8%8F-9e2af8210a60">Všichni mluví o AI modelech. Ale kdo je skutečně dostal do produkce? 🛠️</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[0 Data Loss, 40% Savings: Migration from AWS to Google Cloud]]></title>
            <link>https://medium.com/vortex-cloud/0-data-loss-40-savings-migration-from-aws-to-google-cloud-a0831aa5482e?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0831aa5482e</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[healthtech]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 12:48:12 GMT</pubDate>
            <atom:updated>2026-02-04T13:36:57.737Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Kinetikos Migration Story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32MMAG62baiGi74EEFQA0A.png" /></figure><p>For digital health innovator Kinetikos, infrastructure isn’t just about keeping the lights on — it’s about patient safety. Their AI analyzes human movement to help clinicians diagnose mobility disorders, meaning their backend requires absolute precision.</p><p>In late 2024, Kinetikos reached a limit with their current AWS setup. To scale efficiently, they needed to move to Google Cloud Platform (GCP). The constraints were tight: the migration had to be secure, cost-effective, and executed rapidly.</p><p>Vortex Cloud stepped in to manage the transition. By leveraging Google’s financial incentives and an aggressive engineering timeline, the team executed a full cutover in just two weeks — achieving a zero-data-loss standard.The Technical Reality: Why “Lift and Shift” Wasn’t an Option</p><p>Kinetikos was running a sprawling legacy environment that couldn’t simply be copied and pasted into Google Cloud. The architecture involved a complex web of dependencies:</p><ul><li><strong>20+ RDS PostgreSQL instances</strong> containing critical, synchronized patient data.</li><li><strong>50+ S3 buckets</strong> holding massive biomechanical datasets.</li><li><strong>Mixed Compute Resources:</strong> A combination of 15+ EC2 VMs and ECS container orchestration.</li></ul><p>The biggest hurdle wasn’t volume; it was translation. Moving from AWS ECS to <strong>Google Kubernetes Engine (GKE)</strong> required a granular refactor of Docker files. Simultaneously, the messaging architecture — relying on SQS and RabbitMQ — had to be re-architected for <strong>Google Cloud Pub/Sub</strong> to ensure asynchronous messages weren’t dropped during the switch.</p><h3>The Strategy: Infrastructure as Code &amp; Financial Smarts</h3><p>Vortex Cloud didn’t just move data; they built a Landing Zone designed for the next decade of growth.</p><p><strong>1. Terraform Everything</strong> To eliminate “configuration drift” and human error, the entire environment was deployed using Terraform. This Infrastructure as Code (IaC) approach meant the new environment was compliant by default — crucial for meeting GDPR and HIPAA standards.</p><p><strong>2. The Cost Strategy (0% Service Fees)</strong> Migration costs often kill projects before they start. Vortex Cloud utilized the <strong>Google Partner Service Fund (PSF)</strong> to fully subsidize the professional service fees. This meant Kinetikos paid $0 for the migration labor. Combined with GCP’s sustained use discounts and container optimization, Kinetikos is on track to reduce their monthly cloud spend by <strong>30–40%</strong>.</p><h3>The Cutover</h3><p>On December 14, 2024, the team flipped the switch.</p><ul><li><strong>Data Integrity:</strong> All 20+ databases and 50+ buckets migrated with zero loss.</li><li><strong>Better Tooling:</strong> The move facilitated a switch to GitHub Actions, giving developers a cleaner, faster CI/CD pipeline.</li><li><strong>Performance:</strong> The shift to GKE and Cloud Run has measurably lowered latency for end-users.</li></ul><blockquote><em>“Vortex Cloud navigated our complex infrastructure — from databases to container orchestration — with zero data loss and remarkable speed. They didn’t just move our data; they elevated our entire engineering capability.”<br></em><strong>José Castro, Senior Engineering Manager at Kinetikos</strong></blockquote><h3>Handing Over the Keys</h3><p>Vortex Cloud’s goal wasn’t to create vendor lock-in. Immediately following the migration, the focus shifted to training the Kinetikos team. They are now fully autonomous on GCP, capable of managing their new Kubernetes environments without external support.</p><p><strong>Planning a migration?</strong> If you are dealing with legacy debt or spiraling AWS costs, reach out to <strong>Vortex Cloud</strong>. We can check your eligibility for Google Partner Service Funds to offset your migration costs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0831aa5482e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/0-data-loss-40-savings-migration-from-aws-to-google-cloud-a0831aa5482e">0 Data Loss, 40% Savings: Migration from AWS to Google Cloud</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pro Tips & Hidden Gems of Terraform]]></title>
            <link>https://medium.com/@VortexCloud/pro-tips-hidden-gems-of-terraform-595229ea11df?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/595229ea11df</guid>
            <category><![CDATA[terraform-cloud]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[google-cloud-console]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Wed, 04 Dec 2024 13:00:54 GMT</pubDate>
            <atom:updated>2026-01-21T14:31:02.664Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*YsGpGuWtHmTpNv3HcXwm_w.png" /></figure><p>Let’s talk about one of Terraform’s hidden gems that often goes unnoticed: <strong>Terraform Console</strong>. ☁️</p><p>If you’ve ever felt the need for a “safe space” to experiment with your Terraform configurations without the risk of deploying unwanted changes to your infrastructure, <strong>Terraform Console</strong> is your best friend! 💡</p><h3>What is Terraform Console?</h3><p>The Terraform Console is an <strong>interactive command-line interface (CLI)</strong> tool that is a <strong>sandbox</strong> for testing Terraform expressions, functions, and variables. Instead of running <em>terraform apply</em> and crossing your fingers, you can confidently evaluate how expressions behave or test how your variables resolve — all in real-time.</p><p>Think of it as a playground where you can try Terraform commands without fear of breaking things! 🚧</p><h3>Why Should You Care?</h3><ol><li><strong>Safe Experimentation<br>👉</strong>Debug and validate expressions before applying them to your configuration.<br><strong>👉</strong>Understand how Terraform functions (like join, map, or lookup) work without affecting your live infrastructure.</li><li><strong>Quick Learning Curve<br>👉</strong>If you’re new to Terraform, Console is a great place to learn how variables, resources, and expressions interact.</li><li><strong>Debugging Like a Pro<br>👉</strong>If you’re stuck debugging a complex module or template, Console provides an isolated environment to untangle your logic.</li></ol><h3>How to Use Terraform Console?</h3><p>Getting started is super simple:</p><ol><li><strong>Initialize your Terraform workspace<br></strong>Run <em>terraform init</em> in your configuration directory.</li><li><strong>Start the Console<br></strong>Use the command:<br><em>terraform console</em></li><li><strong>Experiment Freely<br></strong>Test anything you want! Examples:</li></ol><blockquote>Evaluate expressions:<br>&gt; length([“apple”, “banana”, “cherry”])</blockquote><blockquote>3</blockquote><blockquote>Test variables:<br>&gt; var.project_id</blockquote><blockquote>“my-project-id”</blockquote><blockquote>Explore outputs:<br>&gt; output.resource_id</blockquote><blockquote>“Example-id”</blockquote><blockquote>Explore resources:<br>&gt; google_compute_instance.myvm.id</blockquote><blockquote>“projects/my-project-123/zones/us-central1/instances/vm-example-01”</blockquote><p>4. Exit<strong><br></strong>Type <em>exit</em> to leave the Console.</p><p>Note: Variables, outputs and resources need to exist in your Terraform state.</p><h3>Pro Tips for Using Terraform Console</h3><p>✅ <strong>Load Your State<br></strong>Terraform Console automatically reads your state file, meaning you can access and test your current resource outputs in real time.</p><p>✅ <strong>Master Functions<br></strong>Console is ideal for understanding Terraform’s built-in functions, like <em>cidrsubnet</em> for networking or <em>coalesce</em> for default values.</p><p>✅ <strong>Debugging? Bring Your Variables<br></strong>Use <em>terraform console</em> with your <em>.tfvars </em>file to simulate configurations as they would run.</p><h3>Final Thought</h3><p>In a world where infrastructure misconfigurations can be costly 💸, <strong>Terraform Console</strong> empowers you to build confidently and debug efficiently. Whether you’re a beginner or an expert, it’s a must-have tool in your Terraform toolbox.</p><p>👉 What’s your favorite Terraform tip or trick? Let’s share and grow together! 🌱</p><p>#CloudComputing #Terraform #IaC #InfrastructureAsCode #DevOps #LearningInPublic</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=595229ea11df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to Google Cloud Excellence: How to Improve the Cloud Strategy ]]></title>
            <link>https://medium.com/vortex-cloud/guide-to-google-cloud-excellence-how-to-improve-the-cloud-strategy-8c8c7b6caf67?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c8c7b6caf67</guid>
            <category><![CDATA[multicloud-management]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-journey]]></category>
            <category><![CDATA[cloud-innovation]]></category>
            <category><![CDATA[google-cloud]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 09:11:33 GMT</pubDate>
            <atom:updated>2024-11-25T09:11:33.484Z</atom:updated>
            <content:encoded><![CDATA[<h4>Crafting a perfect cloud strategy is like preparing for a mission to the stars. It’s not just about getting off the ground but about ensuring every stage of your journey is seamless, efficient, and geared for success. Whether you’re a cloud novice or a seasoned explorer, this guide will help you refine your strategy, avoid common pitfalls, and unlock the full potential of your cloud environment.</h4><p>Here’s your step-by-step mission briefing:</p><h3>Step 1: Build a Launch-Ready Foundation</h3><p>Every incredible journey begins with solid groundwork. In cloud terms, this means creating a scalable, secure, and resilient cloud foundation that can weather any challenge. Prepare for lift-off by building your cloud foundation.</p><p>🚀 <strong>Key Checklist:</strong></p><ul><li><strong>Assess Readiness:</strong> Is your current IT infrastructure cloud-ready? Take a hard look at compatibility and performance.</li><li><strong>Prioritize Security:</strong> Think of security as your spacecraft’s shield. Implement robust defenses with tools like Google Cloud’s Security Command Center to stay one step ahead of threats.</li><li><strong>Scalable architecture:</strong> Use automation tools like Terraform or Ansible to design infrastructure that adapts to your evolving needs.</li></ul><p>✨ <strong>Why It Matters:</strong> Cutting corners here is like building a spaceship without testing the engines — it might work, but do you really want to risk it?</p><h3>Step 2: Empower Your Crew</h3><p>Even the best spaceship won’t go far without a skilled crew. The same is true for your cloud journey. Upskilling your team ensures they can navigate any challenge with confidence and expertise.</p><p>💡 <strong>Upgrade Your Team’s Toolbox:</strong></p><ul><li><strong>Tailored Training:</strong> Offer specialized workshops for developers, DevOps teams, and IT professionals to master core cloud skills.</li><li><strong>Certify the Experts:</strong> Encourage your team to pursue certifications like Google Cloud’s Professional Cloud Architect or Data Engineer to stay sharp and credible.</li></ul><p>💬 <strong>Pro Tip:</strong> Knowledge isn’t just power — it’s your rocket fuel. An empowered team will spot opportunities, solve problems, and drive innovation faster than ever.</p><h3>Step 3: Optimize and Govern Like a Pro</h3><p>As your cloud journey takes off, the next mission is optimizing operations and ensuring smooth governance. This is where you fine-tune your strategy for maximum cloud performance and cost-efficiency.</p><p>🔧 <strong>Optimization Tactics:</strong></p><ul><li><strong>Master Cloud Economics:</strong> Take advantage of pricing models like Sustained Use Discounts and implement cost-saving measures like auto-scaling and right-sizing.</li><li><strong>Govern with Precision:</strong> Use tools like Google Cloud Monitoring and Logging to establish policies, track performance, and stay compliant.</li><li><strong>Create Landing Zones:</strong> These act as base camps for managing resources effectively and securely.</li></ul><p>💰 <strong>Did You Know?</strong> Businesses that actively optimize their cloud resources see up to 25% in annual cost savings.</p><h3>Step 4: Innovate, Don’t Just Operate</h3><p>Now that you’ve reached orbit, it’s time to innovate! This is where your cloud journey transforms from operational excellence to competitive advantage. Innovation is the secret sauce that helps you stand out in today’s crowded digital landscape. Unlock the potential of AI, data analytics, and DevOps to accelerate your business and drive future growth.</p><p>🌟 <strong>Unlock New Horizons:</strong></p><ul><li><strong>AI/ML to the Rescue:</strong> Use tools like Vertex AI and BigQuery ML to uncover trends, automate processes, and supercharge decision-making.</li><li><strong>Adopt DevOps Practices:</strong> Accelerate product cycles with CI/CD pipelines and hybrid cloud solutions like Kubernetes.</li><li><strong>Go Big with Data Analytics:</strong> Connect your cloud with platforms like Snowflake or BigQuery to make informed, data-driven decisions.</li></ul><p>🎯 <strong>Pro Tip:</strong> Don’t just follow trends — create them. Innovating with cloud-native tools positions you as a leader in your industry.</p><h3>Step 5: Keep Evolving</h3><p>The cloud isn’t a one-and-done solution; it’s a dynamic system that grows and adapts alongside your business. Continuous improvement is the key to staying relevant. Keep monitoring, analyzing, and innovating with new cloud features. Continuously assess your cloud strategy and stay ahead.</p><p>🔄 <strong>Always Be Improving:</strong></p><ul><li><strong>Monitor Everything:</strong> Regularly assess your cloud performance and identify areas for improvement.</li><li><strong>Plan for the Worst:</strong> Using tools like Google Cloud Storage, a disaster recovery strategy ensures you’re ready for any emergency.</li><li><strong>Future-Proof Your Strategy:</strong> Keep up with emerging technologies and evolving cloud features to stay ahead.</li></ul><p>🌍 <strong>Reality Check:</strong> The cloud isn’t a destination — it’s a journey. Regular evaluations keep your strategy aligned with your business goals and market demands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvgdezIQ9Ti-PNqmkTU_yA.png" /><figcaption>Vortex, in collaboration with Google Cloud, has introduced #VortexLaunchpad — an initiative designed to simplify and supercharge the cloud journey significantly.</figcaption></figure><h3>Why Vortex Launchpad?</h3><p>At <strong>Vortex</strong>, we specialize in making your cloud journey smoother, smarter, and infinitely more rewarding. Whether it’s designing your foundational architecture or unlocking cutting-edge AI/ML capabilities, we’ve got you covered.</p><p><strong>Here’s how we help:</strong></p><ul><li><strong>Migration Strategies:</strong> We make transitions seamless, whether it’s Lift &amp; Shift or a full re-platform.</li><li><strong>Custom Workshops:</strong> Upskill your team with tailored training and practical hands-on labs.</li><li><strong>Ongoing Optimization:</strong> From cost control to innovation reviews, we ensure your cloud stays future-ready.</li></ul><h3>Your Cloud Mission Awaits</h3><p>Every organization’s cloud journey is unique, but one thing remains constant: success comes to those who come prepared. With the right foundation, an empowered team, and a clear focus on innovation, your business can transcend boundaries and achieve incredible things.</p><p><strong>Ready to launch?</strong> Let’s turn your cloud strategy into a powerhouse of innovation and efficiency. Reach out to us at<a href="https://vortexcloud.io/"> vortexcloud.io</a>, and let’s chart your course to the stars. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c8c7b6caf67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/guide-to-google-cloud-excellence-how-to-improve-the-cloud-strategy-8c8c7b6caf67">Guide to Google Cloud Excellence: How to Improve the Cloud Strategy 🚀</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamically Generating MERGE Queries with BigQuery’s Procedural Language]]></title>
            <link>https://medium.com/vortex-cloud/dynamically-generating-merge-queries-with-bigquerys-procedural-language-7f27cbd5b3cc?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f27cbd5b3cc</guid>
            <category><![CDATA[scripting]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[merge-queries]]></category>
            <category><![CDATA[scripting-language]]></category>
            <category><![CDATA[bigquery]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Wed, 29 May 2024 09:37:10 GMT</pubDate>
            <atom:updated>2024-05-29T09:37:12.228Z</atom:updated>
            <content:encoded><![CDATA[<p>BigQuery’s scripting language, a highly scalable data warehouse, offers powerful yet understated features. While many data professionals are familiar with its capabilities, fewer have tapped into the advanced tools it provides for automating repetitive tasks. This includes the ability to dynamically create and update queries on the fly, relieving you from the burden of manual maintenance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*bYorYwC45K-EKjrYArrBmg.png" /></figure><h3>Backstory</h3><p>We utilized BigQuery as our data warehouse, with around 200 tables from various sources. Whenever new data was received, it was first stored in the landing zone. After that it was upserted to target tables using a MERGE query, stored and executed in Cloud Composer. These MERGE queries were static and hardcoded for each table in our target zone.</p><p>Each time a new table had to be synced, a new MERGE query had to be painstakingly crafted. Even a simple change like adding or removing a column required altering the existing query. Each change consumed about 2 hours of preparation, testing, and deployment time.</p><p>With 200 tables to sync and more expected, our current method was not scalable. However, our exploration of BigQuery’s procedural language reassured us that we could find a better, more scalable approach.</p><h3>Utilizing FOR…IN loop to create queries dynamically</h3><p>Asour tables are several hundred GBs in size and require refreshing every hour, we needed to keep the processing within BigQuery.</p><p>Realizing the limitations of our current approach, we turned to BigQuery’s procedural language for a solution. By populating all elements of the MERGE query from the BigQuery’s information schema, we could generate synchronization queries on the fly. This approach covered all scenarios, from column changes to the addition of new tables, making our syncing process more dynamic and adaptable.</p><p>Many loops are available in the BigQuery procedural language, but for our use case, the FOR…IN loop was perfect, as it allowed us to loop over all tables present in the target dataset and sync the data from staging dataset (landing zone).</p><p>To fully automate the process, our query had to do the following steps:</p><ol><li><strong>Get a list of tables to sync and loop over each table</strong></li><li><strong>Get a list of columns for the table</strong></li><li><strong>Get the primary key (for joining) and partitioning key (for partition pruning)</strong></li><li><strong>MERGE the staging and target table using all of the above</strong></li></ol><p>As was already mentioned, all of the above information is available in the INFORMATION_SCHEMA, and after the information is retrieved, the queries can easily be formatted and executed using BigQuery built-in functions.</p><p>Here’s how we put it into action with a FOR…IN loop:</p><pre><br><br>DECLARE insert_columns, update_columns, pk_column, part_column STRING;<br>DECLARE date_arr ARRAY &lt;DATE&gt;;<br><br>FOR record IN (<br>                 SELECT<br>                     table_schema || &#39;.&#39; || table_name   AS table_id<br>                   , &#39;staging_data&#39; || &#39;.&#39; || table_name AS staging_table_id<br>                   , table_schema<br>                   , table_name<br>                 FROM main_data.INFORMATION_SCHEMA.TABLES<br>             )<br>   DO<br><br>       -- read columns from schema<br>       EXECUTE IMMEDIATE FORMAT(&#39;&#39;&#39;<br>       SELECT STRING_AGG(column_name), STRING_AGG(&#39;tgt.&#39; || column_name || &#39;=src.&#39; || column_name)<br>       FROM %s.INFORMATION_SCHEMA.COLUMNS<br>       WHERE table_name = &#39;%s&#39;<br>       &#39;&#39;&#39;, record.table_schema, record.table_name) INTO insert_columns, update_columns;<br><br>       -- get primary key from schema<br>       EXECUTE IMMEDIATE FORMAT(&#39;&#39;&#39;<br>       SELECT column_name<br>       FROM %s.INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE<br>       WHERE table_name = &#39;%s&#39;<br>       AND constraint_name LIKE &#39;%%pk$&#39;<br>       &#39;&#39;&#39;, record.table_schema, record.table_name) INTO pk_column;<br><br>       -- get partition key from schema<br>       EXECUTE IMMEDIATE FORMAT(&#39;&#39;&#39;<br>       SELECT column_name<br>       FROM %s.INFORMATION_SCHEMA.COLUMNS<br>       WHERE table_name = &#39;%s&#39;<br>       AND is_partitioning_column = &#39;YES&#39;<br>       &#39;&#39;&#39;, record.table_schema, record.table_name) INTO part_column;<br><br>       -- get array of dates to sync for partition pruning<br>       EXECUTE IMMEDIATE FORMAT(&#39;SELECT ARRAY_AGG(DISTINCT DATE(%s)) FROM %s&#39;<br>           , part_column, record.staging_table_id) INTO date_arr;<br><br>       -- construct and execute final MERGE statement<br>       EXECUTE IMMEDIATE FORMAT(&#39;&#39;&#39;<br>       MERGE %s<br>       USING %s src<br>       ON src.%s = tgt.%s<br>       AND DATE(tgt.%s) IN UNNEST(date_arr)<br>       WHEN MATCHED THEN UPDATE SET %s<br>       WHEN NOT MATCHED THEN INSERT (%s) VALUES (%s);<br>       &#39;&#39;&#39;, record.table_id, record.staging_table_id, pk_column, record.updated_column, pk_column, pk_column, part_column, update_columns,<br>                                insert_columns, insert_columns);<br><br><br>   END FOR;</pre><h3>Debugging and costs</h3><p>Debugging or optimizing the queries is straightforward with BigQuery’s procedural language. Each query in each loop iteration is logged as a separate child job of the parent for loop job, allowing you to easily track billed bytes or potential errors for every part of the process. This transparency instils confidence in the reliability of the solution.</p><p>However, there is a slight increase in costs associated with this approach since BigQuery bills you at least 10MB for any query against the INFORMATION_SCHEMA (<a href="https://cloud.google.com/bigquery/docs/information-schema-intro#pricing">https://cloud.google.com/bigquery/docs/information-schema-intro#pricing</a>). However, we determined that this cost increase is negligible, especially compared to the engineer’s time.</p><h3>Conclusion</h3><p>By leveraging BigQuery’s procedural language, we’ve significantly streamlined our data management, making it more efficient and less reliant on manual intervention. This has enabled our engineers to focus on more important tasks without impacting the debugging process of the queries. Moreover, the cost has remained unchanged and imperceptible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f27cbd5b3cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/dynamically-generating-merge-queries-with-bigquerys-procedural-language-7f27cbd5b3cc">Dynamically Generating MERGE Queries with BigQuery’s Procedural Language</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tagging Your Cloud Resources: How to Improve Your Cloud Financial Management Strategy?]]></title>
            <link>https://medium.com/vortex-cloud/tagging-your-cloud-resources-how-to-improve-your-cloud-financial-management-strategy-4721dbdc1aed?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4721dbdc1aed</guid>
            <category><![CDATA[cloud-optimization]]></category>
            <category><![CDATA[cloud-financial]]></category>
            <category><![CDATA[cloudfinancialmanagement]]></category>
            <category><![CDATA[cloud-strategy]]></category>
            <category><![CDATA[cloud-resource]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Fri, 08 Mar 2024 11:58:00 GMT</pubDate>
            <atom:updated>2024-03-11T06:55:20.698Z</atom:updated>
            <content:encoded><![CDATA[<p>Looking at traditional industries, such as manufacturing, they clearly understand the costs associated with each component of their production process. Manufacturers meticulously track expenses for raw materials, labour, equipment, and other factors contributing to the overall cost of producing, marketing, and selling their goods. This detailed knowledge empowers them to optimise their processes, reduce waste, and make informed decisions about pricing and profitability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXSMM_W8Oa_eqPok67LJ9Q.png" /></figure><h3>Efficient cloud financial management</h3><p>As a founder or leader of a startup, it is worth asking yourself:</p><ul><li>Do I have comparable insight into the costs associated with each component of my cloud-based infrastructure?</li><li>Can I accurately track and allocate expenses for my cloud services?</li><li>Do data drive my decision-making process?</li><li>How do I track and measure my KPIs?</li></ul><p>If the answer is unclear or uncertain, it is time to reevaluate your Cloud Financial Management strategy. Efficient cloud financial management has become crucial for numerous aspects, such as informed decision-making, governance, automation, and budgeting. The implementation of the Tagging Strategy plays a significant role in this.</p><p>The Tagging Strategy is built upon utilizing metadata such as <a href="https://www.linkedin.com/showcase/google-cloud/">Google Cloud</a> Labels, <a href="https://www.linkedin.com/company/amazon-web-services/">Amazon Web Services (AWS)</a> Tags, <a href="https://www.linkedin.com/company/msnazure/">Careem Exchange</a> Tags, or other cloud providers’ equivalents. These key-value pairs allow everyone from executives and financial planners to developers and product managers to categorize and organize resources, simplifying their managing, searching, filtering, and reporting.</p><h3>The tagging strategy brings several benefits to the table:</h3><ol><li>Cost allocation enables more granular cost reporting and analysis by associating expenses with specific projects, departments, or teams. This insight allows companies to make informed decisions about product pricing and measure the ROI of their initiatives.</li><li>Resource organization becomes more manageable as tags and labels help categorize resources by purpose, owner, environment, or other relevant criteria, promoting accountability within the organization.</li><li>Access control where tags and labels can be used to implement access policies that ensure only authorized users can manage specific resources.</li><li>Even automation is facilitated by the tagging strategy as it provides triggers for scripts and other automated processes, such as terminating instances or monitoring machines with specific tags.</li></ol><h3>Let’s take the below example</h3><p>A group of resources that are tagged with the following values:</p><p>environment: research / product: product_a / team: team_c / function: ai_model_a.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/0*Bm-wLToxnbeOjEZu" /></figure><p>According to these tag values, we could answer questions like: How much does team_c cost to train ai_model_a related to product_a within the research environment?</p><p>Questions like this could help us evaluate future development, understand the potential ROI, or even identify inefficiencies related to executing the ai_model_a in that specific case.</p><p>In other cases, we could create a governance policy in which each resource tagged with the above values is automatically terminated at night and on weekends. We all know how expensive GPUs can be, so proactively preventing inefficiency could be very beneficial.</p><p>To maintain order and efficiency, companies adhere to several best practices:</p><ul><li>Consistency: They establish a consistent tagging and labelling scheme across all resources to simplify management and reduce confusion.</li><li>Documentation: They document the tagging and labelling strategy, including the key-value pairs used and their purpose, to ensure adherence across the organization.</li><li>Enforcement: They implement mechanisms to enforce the tagging and labelling strategy, such as using automated tools to apply tags and labels to newly created resources.</li><li>Review: They periodically update the tagging and labelling strategy to ensure its relevance and effectiveness.</li></ul><p>The use of tags exposes numerous challenges, out of which one prevails, and that is the formulation of the strategy itself.</p><p>Other challenges may involve shared costs, implementation, granularity levels, etc. With a team of experts from diverse disciplines, Vortex can effectively identify your requirements and assist you in deriving greater value from your data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4721dbdc1aed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/tagging-your-cloud-resources-how-to-improve-your-cloud-financial-management-strategy-4721dbdc1aed">Tagging Your Cloud Resources: How to Improve Your Cloud Financial Management Strategy?</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FinOps is okay, but CloudEconomics is superior!]]></title>
            <link>https://medium.com/vortex-cloud/finops-is-okay-but-cloudeconomics-is-superior-cdee83c3d801?source=rss-16c38efb6a6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdee83c3d801</guid>
            <category><![CDATA[cloud-analytics]]></category>
            <category><![CDATA[cloud-economics]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-cost-optimization]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Vortex]]></dc:creator>
            <pubDate>Wed, 28 Feb 2024 10:44:13 GMT</pubDate>
            <atom:updated>2024-02-28T10:47:12.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tsFeccaUidrr7XakdEF3cw.png" /></figure><p>Cloud FinOps is a term used to describe the financial operations and management of cloud computing resources. It involves optimizing costs, increasing efficiency, and improving return on investment.</p><p>Initially, cloud FinOps focused on cost optimization through a variety of strategies, including analyzing usage patterns, identifying waste, and negotiating discounts. This approach effectively reduced cloud costs, but it did not fully capture, and in fact, it missed, the potential of cloud economics to drive business growth.</p><p>To this day, cloud FinOps services, technologies and specialized partners all focus on the same trivial and basic aspects: underutilized and rightsizing resources, waste, and commitments in return for discounts.</p><p>As companies began to adopt cloud computing more widely, the role of FinOps expanded to encompass broader economic considerations.</p><h3>The Evolution of Cloud FinOps to Cloud Economics</h3><p>It reflects a shift in focus from simply managing cloud costs to leveraging cloud technology to drive business value.</p><h3>Cloud Economics takes advantage of using cloud technology to:</h3><ul><li>create new business opportunities,</li><li>improve customer experiences,</li><li>accelerate innovation.</li></ul><p>This requires a more strategic approach to cloud management that goes beyond simple cost optimization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RZXCAu6-85xxDjyK" /></figure><p>Cloud economics involves leveraging hashtag#cloudtechnology to drive business value through improved agility, enhanced hashtag customer experiences, or new revenue opportunities. This approach requires a deep understanding of both the technical capabilities of cloud computing and the business needs of the organization by focusing on and diving deep into the realm of hashtag#UnitEconomics.</p><blockquote><em>To fully realize the potential of Cloud Economics, companies, especially C-level management must embrace and lead a culture of innovation and change. Management needs to join and be part of the cloud journey by drawing relevant business-critical hashtag#insights from their hashtag#cloudinfrastructure. By doing so, organizations can use cloud technology to drive innovation and create new opportunities for growth.</em></blockquote><h3>In summary:</h3><p>The evolution of cloud FinOps to Cloud Economics reflects a broader shift in the role of cloud computing within organizations. While cost optimization remains important, the focus has expanded to include broader economic considerations and a more strategic approach to hashtag cloud management. By embracing cloud economics, organizations can use cloud technology to drive calculated, measured and educated new growth opportunities.</p><p><strong>Author:</strong> <a href="https://www.linkedin.com/in/ranrothschild/">Ran Rothschild</a>, Founder &amp; CBO in Vortex</p><p><strong>Vortex | About us</strong></p><p>We are revolutionizing the role of your cloud partner and trusted advisor. With years of experience in mature markets and a unique relationship with Google, we provide comprehensive tools, support and solutions to help your business grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdee83c3d801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vortex-cloud/finops-is-okay-but-cloudeconomics-is-superior-cdee83c3d801">FinOps is okay, but CloudEconomics is superior!</a> was originally published in <a href="https://medium.com/vortex-cloud">Vortex Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>