Henrik Lindberg

Microservices get a bad rap due to complexity and high TCO. A lot of that is because a microservice-based application works the same way as a bunch of dominoes falling. If one misses, or falls out of order, the whole workflow stops. And you have no control over the process once your microservices start ping-ponging events and RPC's back and forth. That's why #microservices are so expensive to manage. Great blog post below by Colt McNealy about how LittleHorse can solve those problems. Give it a read. https://lnkd.in/gJECBwRu

58

I just updated my first table format comparison blog post to fix some missing details of Apache Hudi. https://lnkd.in/dwSUS6qS

5

🎥 New Video: Master System Testing in Kubernetes with Testkube! 🚀 Our latest video shows how Testkube simplifies the process. Watch now to build a real-world test scenario in minutes! 👇 https://bit.ly/4doZjKa #Kubernetes #SystemTesting #DevOps #Testkube #CloudNative

1

🎥 New Video: Master System Testing in Kubernetes with Testkube! 🚀 Our latest video shows how Testkube simplifies the process. Watch now to build a real-world test scenario in minutes! 👇 https://bit.ly/4doZjKa #Kubernetes #SystemTesting #DevOps #Testkube #CloudNative

1

Missed one aspect of writing the TLA+ spec yesterday. How to gain confidence it is correct. https://lnkd.in/dQn2VUUq

8

With the announcement of S3-native-streams (Freight clusters), here is a commentary on Confluent strategy regarding object storage, streaming and an open data architecture. https://lnkd.in/dTg6DKVy

49

6 Comments

An insightful discussion with Dave Neary, Ricardo Rocha from CERN, and Victor Jakubiuk on the challenges of enhancing efficiency and sustainability of AI inference workloads on Kubernetes in the latest Ampere Developer Impact video #cloudnative #ampere #AI #Kubernetes #Efficiency #Sustainability

33

4 Comments

Is your observability bill out of control? Are you wasting engineering time trying to justify the cost? There's a better solution… https://hubs.la/Q02PsJZM0 #kubernetes #devops #cloud #observability

10

A K8s cluster is a complex orchestration of a vast multitude of components. Having the right instrumentation strategy of the cluster is essential, not just for optimization, but for operability and reliability as well. Here's a quick guide to what a well optimized K8s looks like. #Kubernetes #K8s #Compute #Cloud #SaaS https://lnkd.in/gzUSisQk

12

What is WarpStream by Confluent? How does it differ from every other hosted Kafka service? Tim Berglund, answers these questions and more in our latest lightboard video. Watch and learn the different ways cloud offerings manage storage and compute resources, the trade-offs inherent in traditional BYOC offerings, and how WarpStream provides a more secure and more cloud-native solution. Learn more in our blog -> https://cnfl.io/4cTqVGc

205

2 Comments

The transition to strong consistency involved moving schema and topology metadata to #Raft, implementing a centralized topology coordinator, and changes to our commit logs, schema versioning, authentication, and database internals. Kostja Osipov explains how we moved to a new algorithm and its implications for elasticity, operability, and performance. https://lnkd.in/e_Vn4W85 #ScyllaDB #NoSQL #database #techtips #opensource

21

Appchains are so appealing to devs and are so popular. But do we really need an expensive L2 or a sidechain or a zone or parachain for Appchains? We argue not. Enter Supra Containers - Appchains on Supra L1. #blockchain #appchain #L2

16

The ecosystem’s now crafting platforms atop Kubernetes, stitching together GitOps tools, application descriptors, and infrastructure management for custom APIs. But, can we push beyond Kubernetes’ framework limitations? #vshntimer https://lnkd.in/du4Eg8u2

1

𝐋𝐞𝐯𝐞𝐫𝐚𝐠𝐢𝐧𝐠 𝐂𝐥𝐨𝐮𝐝 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐟𝐨𝐫 𝐋𝐞𝐚𝐧 𝐚𝐧𝐝 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭 𝐓𝐞𝐚𝐦𝐬 𝐂𝐥𝐨𝐮𝐝 𝐄𝐧𝐚𝐛𝐥𝐞𝐬 𝐒𝐦𝐚𝐥𝐥𝐞𝐫, 𝐒𝐦𝐚𝐫𝐭𝐞𝐫 𝐓𝐞𝐚𝐦𝐬 Building on a previous post, which concluded that cloud services aren't more expensive than on-premises solutions (https://lnkd.in/d4c32w3b), let's explore how the cloud empowers smaller teams. In developing our online charging system (OCS) for telecom operators as a cloud-native application, we started with a handful of team members, proving large teams aren't needed with the right tools. 𝐓𝐡𝐞 𝐏𝐨𝐰𝐞𝐫 𝐨𝐟 𝐆𝐞𝐧𝐞𝐫𝐚𝐥𝐢𝐬𝐭𝐬 Cloud-native environments offer many services. While mastering all is impossible, generalists can quickly learn and use these services effectively. This adaptability allows team members to switch between container clusters, databases, and other services without deep specialization, maximizing cloud benefits. Prioritizing business value over infrastructure management allows teams to fully utilize available services. 𝐅𝐨𝐜𝐮𝐬𝐢𝐧𝐠 𝐨𝐧 𝐂𝐨𝐫𝐞 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐋𝐨𝐠𝐢𝐜 Our product’s core—rating and charging—is highly complex. Utilizing serverless solutions and managed services like Lambdas, auto-scaling groups, load balancers, and step functions eliminates infrastructure management for necessary but non-core functionalities such as provisioning users. This allows our team to focus on implementing and enhancing core business logic, spending less time on infrastructure and more on adding value through innovative features. 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐚𝐧𝐝 𝐈𝐧𝐝𝐮𝐬𝐭𝐫𝐲 𝐄𝐱𝐩𝐞𝐫𝐭𝐢𝐬𝐞 𝐢𝐧 𝐓𝐞𝐚𝐦𝐬 Balancing technical cloud skills with business and industry knowledge is crucial. While not every team member may possess deep business domain expertise, reducing infrastructure management allows them to focus on core logic development. This ensures our team is technically proficient and aligned with business objectives, fostering a product that drives business value. 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐢𝐧 𝐓𝐞𝐚𝐦 𝐒𝐢𝐳𝐞 𝐚𝐧𝐝 𝐃𝐞𝐯𝐎𝐩𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 A key benefit of cloud adoption is team size flexibility. Projects can start with even one member, limited only by operational needs like on-call schedules and incident response. Integrating DevOps principles allows the same team to handle both development and incident management efficiently, ensuring responsiveness without larger teams. This maintains operational efficiency and reduces failure risks by preventing teams from becoming overextended. 𝐊𝐞𝐲 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 Embracing cloud-native architectures enables organizations to maintain lean, knowledgeable teams focused on delivering real business value. By leveraging managed services and fostering a generalist skill set, companies can reduce overhead, minimize risks, and enhance operational efficiency. This strategic approach ensures teams remain agile and aligned with business objectives.

11

Today we launched the largest collection of improvements to Pulumi ESC since the initial preview launch last fall - all focused on bringing robust software engineering features to secrets and configuration management. This is a key step toward ESC GA planned for later this year, and delivers on three of the most requested ESC features we've heard from users over the last 6 months. 📑 Versioning: Pulumi ESC now supports versioning of environments, allowing you to see and audit every change to the secrets and configuration for an environment, pin references to an environment to a specific version or version tag, and safely roll back an environment to a previous version. 🧰 SDKs: Pulumi ESC now has SDKs available for Python, TypeScript/JavaScript and Go, enabling ESC to be used directly within applications, tools and services to retrieve and manage secrets and configuration values at runtime. 🏗️ Environments as Code with IaC: New support for defining and managing Pulumi ESC environments, secrets, and configuration from within Pulumi IaC programs allows source-controlled environment specification and managing secrets and configuration lifecycles via code. Check out our release announcements: https://lnkd.in/dhqeMFDR.

22

Kubernetes + Postgres = CloudnativePG <3

3