Nordcloud, an IBM Company

You’re responsible for cloud costs. But you can’t see them. And you can’t change them. That’s not ownership. That’s frustration. This is something I see quite often when organisations start with FinOps. Responsibility gets assigned. But the people who are expected to “own” costs don’t have: • the visibility • the context • or the ability to act And then we wonder why nothing changes. Or worse - why it turns into a blame game. FinOps isn’t supposed to work like that. If ownership comes without agency, it doesn’t create accountability. It creates disengagement. People stop caring. Or they push responsibility somewhere else. What actually changes things is much simpler: Give teams visibility into what they’re running. Help them understand the impact of their decisions. That’s when something clicks. Costs stop being abstract. And start becoming something you can act on. In this part of Cloud Core Talks, I sat down with Jake McCracken to talk about where this breaks, and what actually helps teams move from awareness to action. Part 3 of Episode 1 is now live! Jake McCracken #FinOps #CloudCosts #NordcloudNinjas

Calling the Munich Python & AI Community 🐍🤖✨ Excited for the upcoming Pyladies Munich & Munich🥨NLP Summer Meetup at Entrix ! 🌴🍹 Join us for an evening of Python, AI, energy trading, networking, and great conversations with the Munich tech community. Highlights include ☀️ AI-based optimization in energy trading Kseniia Ivanchenko ☀️ Insights on getting hired in the age of AI Christian Buckl ☀️ Networking, drinks, food, and raffle prizes 🎁 Whether you are into Python, NLP, cloud, AI, or simply looking to connect with inspiring people in tech, this meetup is for you! Looking forward to seeing the community there 💛 (link in the comments) Yulia Barabash Daryna Dementieva Laysa Uchoa

Back in Las Vegas after 2 years. At Google Cloud Next 2026, I’m curious to see how the shift towards agentic AI and more autonomous systems is shaping up in practice. Especially when it comes to: ➡️ real-world use cases ➡️ developer tooling ➡️ infrastructure behind it all 📍 Las Vegas | April 22-24 If you’re attending, happy to exchange thoughts - or you can book time with our team here 👇 👉 https://lnkd.in/dkZpHXHr #GoogleCloudNext #GoogleCloud #AgenticAI #Cloud #GCP #NordcloudNinjas

On my way to Google Cloud Next in Las Vegas ✈️🇺🇸 I’m particularly interested in Google’s approach to sovereign cloud in the European context, where the topic is becoming increasingly important. Also looking forward to the latest updates across data and FinOps. It's a 16h flight 😫. Las Vegas, be worth it 😄 Any tips from people who’ve attended before are very welcome. #GoogleCloud #CloudNext #FinOps #Data

❗ You can now ingest data with Lakeflow Connect… without CDC. That sentence should make a lot of data engineers pause. A recent update to Lakeflow Connect introduces query-based ingestion - and it removes one of the biggest friction points for many data teams that either can’t enable CDC or don’t want to take on the operational overhead that comes with it Instead of setting up change CDC system now you just need to: - define a table - pick a cursor column (timestamp / ID) - and Databricks handles incremental loads for you That’s it. Under the hood, it works by tracking a high-water mark and querying only new/updated rows on each run - no gateways, no staging layers, no CDC infra () It works with Oracle, SQL Server, PostgreSQL, MySQL, MariaDB, Teradata, and all other sources supported through Lakehouse Federation. Additionally you can define row filters which get pushed down to the source, so you're only transferring the rows you actually need. It also handles soft and hard deletes, schema evolution, and you can run them on serverless or classic compute making it easier to establish connectivity to your databases. #databricks #dataengineering

Hard to believe its Summit time again, looking forward as always to connecting with customers, both new and existing to share insights from across the ecosystem. After such a huge year in the AI and agentic space Im personally super excited to hear / share stories of some of business benefits that customers have been able to achieve in their production environments. Bring it on!

In Italy, the best conversations don’t always happen in PowerPoint. But over 🍕, 🍝, 🍷 and Grappa 😉. Grazie mille to the team at Helvetia Insurance Italy for hosting us and accommodating us so generously. Great people, great discussions, great espresso ☕️ (One of the last chances to get a picture with the old Helvetia Insurance Switzerland logo)

I have now spent enough time between Germany and Brazil to say this with some confidence: I am equally confused in both places. In Germany, I once got lightly scolded for crossing an empty street at two in the morning. There was no car in sight. Just me, the red light, and a stranger who looked at me as if I had broken something important. In Brazil, I have crossed highways guided by little more than instinct and someone shouting “vai, vai, vai.” And somehow, that also works. My German friends plan dinner weeks in advance. There are calendar invites. There is structure. My Brazilian friends invite me “later,” which could mean in two hours or next week, and both feel correct. I have arrived too early, too late, and once on the wrong day. No one agreed on the plan, but everyone accepted the outcome. I have come to appreciate both. Germany gives me structure and a sense of order. There is comfort in knowing what will happen and when. Brazil gives me energy and openness. Plans are softer, but people are closer. I will probably never fully belong to either place. And yet both feel like home in ways I did not expect. It turns out I need rules. And a little bit of chaos. Alles in Ordnung 🙆🏻♀️

NIS2 makes resilience mandatory. BCDR makes it possible. Across organisations I work with, the same pattern keeps showing up: ➡️strong DR tooling. ➡️unclear business priorities. ➡️slow decision-making when it actually matters. The result? ✅ Systems recover fast. ❌ The business doesn’t. In my latest blog, I break down how to close that gap and why cloud-native DR + strong BC governance is now the standard under NIS2. Because resilience today isn’t about ticking a compliance box. It’s about being able to operate, decide and communicate under pressure. A few key shifts I’m seeing: ⚡ Governance before technology — know what matters before you try to recover it. ⚡ Cloud-native DR — automated, testable, audit-ready by design. ⚡ Real metrics — not just uptime, but impact, decision speed and continuity And most importantly: 1️⃣ Start small. 2️⃣ One critical process at a time. 3️⃣ Then scale. If you’re rethinking your resilience strategy (or being asked to) this is a practical place to begin. https://lnkd.in/ePc8htjF