# vendor lock-in Published articles for vendor lock-in. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend DevFeed: [Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend]() Original publisher: [Read original article]() Author: Gabriele Bartolini (EnterpriseDB) and CNCF Ambassador, Rob Kenefeck (ControlPlane) Published: 2026-09-16T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [CloudNativePG](), [Kubernetes](), [PostgreSQL](), [Open Source](), [vendor lock-in]() Tags: [blog](), [cloudnativepg](), [docker](), [hashicorp-vault](), [helm](), [infrastructure](), [kubernetes](), [linux-foundation](), [open-source](), [postgresql](), [secrets](), [vendor-lock-in]() ### AI overview A tutorial describes deploying OpenBao on Kubernetes with a three-instance CloudNativePG PostgreSQL cluster as its storage backend. It explains certificate-based authentication and a local Kind-based test environment. ### Source excerpt Managing infrastructure secrets on Kubernetes needs a backend that is self-healing and free of vendor lock-in, and that is exactly what OpenBao (the Linux Foundation's open-source fork of HashiCorp Vault) and CloudNativePG give you: an entirely... ## What is bring your own LLM (BYO LLM)? DevFeed: [What is bring your own LLM (BYO LLM)?]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Large Language Model](), [vendor lock-in](), [Artificial Intelligence]() Tags: [agents](), [industry-insights](), [integration](), [large-language-model](), [llm](), [platforms](), [vendor-lock-in]() ### AI overview The article explains bring your own LLM (BYO LLM), an architecture that lets organizations choose and change the large language model powering their AI agents. It describes how Twilio's Agent Connect mediates between selected models and communication channels, preserving context while separating model ownership from platform-provided voice, messaging, streaming, identity, and escalation capabilities. ### Source excerpt Bring your own LLM (BYO LLM) lets you choose the large language model powering your AI agents rather than accepting whatever your platform ships with. ## Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in DevFeed: [Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in]() Original publisher: [Read original article]() Author: Robert Bernier Published: 2026-08-26T14:07:50Z Content type: opinion Language: en Sources: [Blog - Percona]() Topics: [PostgreSQL](), [vendor lock-in](), [Database Migration](), [Open Source]() Tags: [database-migration](), [database-trends](), [insight-for-dbas](), [insight-for-developers](), [migration](), [open-source](), [postgres](), [postgresql](), [vendor-lock-in]() ### AI overview The article examines how commercial ecosystems built around PostgreSQL can create walled-garden effects and constrain the portability of PostgreSQL-compatible systems. It highlights migration complexity, switching costs, and potential data-integrity risks when leaving such ecosystems. ### Source excerpt These days there's been a lot of talk about Postgres having an impact on "everything". Whether it's replacing legacy systems, creating a new greenfield project or even implementing it as a back-end to an agentic AI, Postgres is today's poster child for innovation. So performing something as dull and straightforward as a database migration should ... Continued The post Navigating the Walled Gardens of PostgreSQL: Hidden Risks of Postgres Vendor Lock-in appeared first on Percona. ## The real cost of your observability stack DevFeed: [The real cost of your observability stack]() Original publisher: [Read original article]() Author: Shenoy Pratik Gurudatt Published: 2026-08-07T15:00:00Z Content type: article Language: en Sources: [OpenSearch]() Topics: [observability](), [telemetry](), [agent observability](), [Artificial Intelligence](), [Open Source]() Tags: [agent](), [agents](), [ai](), [ai-agents](), [blog](), [dashboards](), [infrastructure](), [latency](), [logging](), [logs](), [metrics](), [microservices](), [observability](), [open](), [open-source](), [platform](), [platform-engineering](), [technical](), [telemetry](), [traces](), [vendor-lock-in]() ### AI overview The article examines the operational and financial costs of fragmented observability for agentic workloads. It explains that humans and AI agents must move among separate metrics, logging, and tracing tools, which increases investigation time, token usage, latency, integration work, and the risk of losing correlation context. It presents an open-source OpenSearch Observability Stack as an alternative intended to unify logs, traces, and agent telemetry while avoiding per-GB penalties and vendor lock-in. ### Source excerpt AI agents generate 10x the telemetry, and proprietary per-GB pricing punishes you for it. See how the open-source OpenSearch Observability Stack unifies logs, traces, and agent telemetry without vendor lock-in. The post The real cost of your observability stack appeared first on OpenSearch. ## Mastering the 50-state AI maze: A platform strategy for sovereignty DevFeed: [Mastering the 50-state AI maze: A platform strategy for sovereignty]() Original publisher: [Read original article]() Author: Marc Mangus Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [AI Strategy](), [Artificial Intelligence](), [Generative AI](), [Azure](), [Microsoft](), [cloud-infrastructure]() Tags: [ai](), [azure](), [compliance](), [developer](), [healthcare](), [microsoft](), [platform](), [policy](), [regulatory](), [strategy](), [vendor-lock-in]() ### AI overview The article argues that healthcare organizations need platform sovereignty to manage conflicting AI regulations across U.S. states. It presents policy-as-code, golden paths, and internal developer portals as scalable defenses against compliance risk and vendor lock-in, illustrated by a health insurer's costly replacement of Microsoft AI and Azure-based services. ### Source excerpt As state AI laws collide, healthcare organizations face mounting compliance risk and vendor lock-in. Learn why platform sovereignty--policy-as-code, golden paths, and internal developer portals--is the only scalable defense against a 50-state regulatory civil war ## OpenTelemetry: The platform engineer's path to standardized observability DevFeed: [OpenTelemetry: The platform engineer's path to standardized observability]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [OpenTelemetry](), [observability](), [telemetry](), [Instrumentation](), [Traces](), [Kubernetes]() Tags: [cncf](), [incident](), [instrumentation](), [kubernetes](), [logs](), [metrics](), [observability](), [opentelemetry](), [platform](), [sdks](), [telemetry](), [traces](), [vendor-lock-in]() ### AI overview This article explains how OpenTelemetry standardizes observability across platform services by providing vendor-neutral APIs, SDKs, semantic conventions, and a Collector for routing and processing telemetry. It connects logs, metrics, and traces while allowing teams to choose analysis backends later, reducing fragmentation and vendor lock-in. ### Source excerpt Standardize observability across your platform with OpenTelemetry. Eliminate fragmented telemetry, reduce incident resolution time, and avoid vendor lock-in. ## OpenTelemetry Has Graduated... Now what? DevFeed: [OpenTelemetry Has Graduated... Now what?]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-15T18:59:02Z Content type: opinion Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [telemetry](), [Open Source](), [vendor lock-in](), [Instrumentation](), [Traces]() Tags: [cncf](), [instrumentation](), [open-source](), [opentelemetry](), [telemetry](), [traces](), [tracing](), [vendor-lock-in]() ### AI overview This article discusses OpenTelemetry's CNCF graduated status, its history as a unified standard for traces, logs, and metrics, and the role of standardized APIs, language implementations, and the Collector in reducing vendor lock-in. ### Source excerpt In case you missed it: OpenTelemetry (OTel) has officially achieved CNCF graduated status! It now stands proudly alongside amazing open source projects such as Kubernetes and Prometheus, to name just a few. It's been a long journey, and we're very excited... But, now what? To understand where we're going, it's important to understand where we came from. History In the not-so-distant past, telemetry signals were not standardized. This meant telemetry formats differed from tool to tool, with each telemetry vendor creating and maintaining its own instrumentation libraries. Vendor lock-in was a huge problem: If you wanted to switch vendors, you had to strip out the previous vendor's libraries from your code and replace them with the new vendor's libraries. As a result, switching vendors was a nontrivial task. ## Keycloak experimental AuthZEN Support DevFeed: [Keycloak experimental AuthZEN Support]() Original publisher: [Read original article]() Author: Ryan Emerson Published: 2026-05-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [openid](), [API](), [REST API](), [interoperability](), [vendor lock-in]() Tags: [authentication](), [changes](), [idm](), [interoperability](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [release](), [resource](), [rest-api](), [saml](), [sdks](), [sso](), [vendor-lock-in](), [works]() ### AI overview Keycloak announces experimental support for the OpenID AuthZEN Authorization API 1.0 specification starting with version 26.7.0. The feature lets Keycloak act as a Policy Decision Point and expose existing authorization policies through a standardized API for Policy Enforcement Points. ### Source excerpt We are excited to announce that from 26.7.0, Keycloak will include experimental support for the OpenID AuthZEN Authorization API 1.0 specification. This allows Keycloak to act as a Policy Decision Point (PDP), exposing its authorization capabilities through a standardized API that any Policy Enforcement Point (PEP) can consume. You can try this now with the Keycloak nightly release. Why AuthZEN? Authorization has long been fragmented, with competing systems defining their own protocols for answering the same fundamental question: "Can this subject perform this action on this resource?". This means applications are tightly coupled to whichever authorization backend they choose, and swapping providers requires rewriting integration code. AuthZEN changes this by defining a single, vendor-neutral API between the component that asks (the PEP) and the component that decides (the PDP). It is, in many ways, what OpenID Connect did for authentication -- but for authorization. With AuthZEN: No more vendor lock-in -- your application speaks one API regardless of the PDP behind it. RBAC, ABAC, and ReBAC under one roof -- different policy models can answer the same request format, enabling true interoperability across authorization paradigms. Centralized, externalized authorization -- policy logic lives in the PDP, not scattered across application code, making it easier to audit and update. Simpler integration -- a clean REST API with a minimal request/response model replaces complex, implementation-specific SDKs. A growing ecosystem OpenID AuthZEN Interop demonstrates that over a dozen independently-developed PDPs can be used interchangeably by the same PEP without changing a single line of application code. By adding AuthZEN support, Keycloak joins this ecosystem and lets you leverage your existing Keycloak policies through the same standardized API used by every other AuthZEN-compatible PDP. How it works The interaction between your application and Keycloak follows the standard PE ## wasmCloud v2.0 is here DevFeed: [wasmCloud v2.0 is here]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-23T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [WebAssembly](), [Cloud Native Ecosystem](), [Kubernetes](), [Command-line interface](), [Containers](), [Development]() Tags: [cli](), [cloud-native](), [containers](), [go](), [kubernetes](), [native](), [operator](), [rust](), [typescript](), [vendor-lock-in](), [wasi](), [wasm](), [wasm-components](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud v2.0 is a redesigned platform for deploying WebAssembly workloads across clouds, Kubernetes clusters, datacenters, and edge locations. The release introduces a simplified runtime architecture, Kubernetes-native scheduling, Wasm Shell, a workload API, and a Kubernetes Operator. ### Source excerpt wasmCloud v2.0 is a reimagining of the wasmCloud platform: Kubernetes-native, radically simplified, and more powerful than ever. ## Supabase Template is Now Available on DigitalOcean App Platform DevFeed: [Supabase Template is Now Available on DigitalOcean App Platform]() Original publisher: [Read original article]() Author: Bikram Gupta Published: 2026-02-26T16:43:31Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Supabase](), [Digital Ocean](), [Template](), [backends](), [PostgreSQL](), [Authentication](), [REST API](), [Security](), [Self-hosted](), [vendor lock-in]() Tags: [api](), [authentication](), [backend](), [digitalocean](), [open-source](), [platform](), [postgresql](), [product-updates](), [real-time](), [rest-api](), [sdks](), [security](), [self-hosted](), [storage](), [vendor-lock-in]() ### AI overview DigitalOcean App Platform now offers native Supabase template support. The template deploys a production-ready Supabase backend with managed PostgreSQL, authentication, REST APIs, file storage, and real-time capabilities. ### Source excerpt Modern applications need more than just a database. They need authentication, auto-generated APIs, file storage, and real-time subscriptions. Supabase is a powerful open-source Firebase alternative that transforms PostgreSQL into a complete backend platform. With its developer-friendly SDKs and instant API generation, Supabase is a top request from teams who want full control over their infrastructure without sacrificing speed. Today, we're excited to announce native Supabase template support on DigitalOcean App Platform. Deploy a production-ready Supabase backend with one click, complete with managed PostgreSQL, authentication, REST API, file storage, and real-time capabilities. Benefits Instant Backend: Get authentication, auto-generated REST APIs, file storage, and real-time subscriptions without writing backend code. Production-Ready Security: Every deployment includes JWT authentication, Row Level Security (RLS), and secure credential management out of the box. Self-Hosted Control: Keep your data, auth credentials, and file storage on infrastructure you control--no vendor lock-in. Full-Stack Ready: Deploy Supabase alongside your frontend application in a single App Platform project. Architecture Overview The Supabase template deploys a complete backend stack that auto-generates APIs from your PostgreSQL schema. Your frontend applications connect through four specialized services that handle data, authentication, files, and real-time updates. How Supabase Works Unlike traditional backends where you write API endpoints manually, Supabase auto-generates them from your database schema: Row Level Security (RLS) policies on your tables control who can access what - users only see their own data, automatically. How to Get Started The template repository contains everything you need to deploy Supabase on App Platform: github.com/AppPlatform-Templates/supabase-appplatform You have three deployment paths: One-Click: Use the Deploy to DigitalOcean button in the repository ## ACP Brings JetBrains on Board DevFeed: [ACP Brings JetBrains on Board]() Original publisher: [Read original article]() Author: Franciska Dethlefsen Published: 2025-10-06T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Protocol (disambiguation)](), [ide](), [IntelliJ IDEA](), [junie](), [PyCharm](), [webstorm](), [codex]() Tags: [codex](), [gemini](), [integration](), [integrations](), [intellij](), [intellij-idea](), [jetbrains](), [junie](), [protocol](), [pycharm](), [vendor-lock-in]() ### AI overview JetBrains will co-develop the Agent Client Protocol with Zed and plans to add ACP support across its IDE ecosystem, including IntelliJ IDEA, PyCharm, and WebStorm. The article presents ACP as an open standard intended to let agents work across compatible editors. ### Source excerpt The Agent Client Protocol reaches a major milestone: JetBrains is committing to bringing ACP support to their entire ecosystem. ## Avoiding Vendor Lock-in with a Compatible, Migration-Friendly, Transparent Container Distro DevFeed: [Avoiding Vendor Lock-in with a Compatible, Migration-Friendly, Transparent Container Distro]() Original publisher: [Read original article]() Published: 2025-09-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [Linux](), [interoperability](), [migration](), [CI/CD](), [toolchain](), [Open Source]() Tags: [arm](), [chainguard-migration](), [chainguard-os](), [ci-cd](), [compatibility](), [container](), [distro](), [linux](), [migration](), [migration-guide](), [oci](), [open-source](), [sboms](), [supply-chain](), [toolchain](), [vendor-lock-in](), [wolfi](), [x86]() ### AI overview The article explains how to evaluate a Linux distribution for containerized workloads while reducing vendor lock-in. It emphasizes compatibility with existing toolchains and CI/CD workflows, transparent build processes, migration ease, interoperability, and adherence to standards such as OCI, CycloneDX, and SPDX. ### Source excerpt Learn how to evaluate and select the right Linux distribution to satisfy your team's needs, simplify migration, and avoid vendor lock-in. ## Redpanda 25.2: Advancing Iceberg integrations for the real-time lakehouse DevFeed: [Redpanda 25.2: Advancing Iceberg integrations for the real-time lakehouse]() Original publisher: [Read original article]() Author: Matt Schumpert Published: 2025-08-05T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Apache Iceberg](), [real-time](), [AWS Glue](), [databricks](), [Event-Streaming](), [interoperability](), [Streaming](), [migration](), [Kafka](), [data]() Tags: [analytics](), [architecture](), [aws-glue](), [aws-glue-catalog-integration](), [databricks](), [databricks-unity-catalog-integration](), [event-streaming](), [iceberg-capabilities](), [integration](), [interoperability](), [kafka](), [kafka-json-schema-mapping](), [low-latency](), [migration](), [open-source-ai-connectors](), [real-time](), [real-time-data-lakes](), [real-time-lakehouse-architecture](), [redpanda-25-2-release](), [redpanda-iceberg-integration](), [schema-registry-authorization](), [streaming-data-analytics](), [streaming-platform-updates](), [vendor-lock-in]() ### AI overview Redpanda 25.2 expands Iceberg integration for a real-time open lakehouse architecture. It adds integrations with Databricks Unity Catalog and AWS Glue Catalog, supports AWS Glue as an Iceberg REST Catalog for Redpanda Iceberg Topics, and expands schema support. The release also includes migration improvements from Confluent and Schema Registry Authorization updates, while emphasizing Kafka client compatibility, low-latency ingestion, open interoperability, and reduced vendor lock-in. ### Source excerpt Check what's new in Redpanda 25.2 as we expand our Iceberg capabilities, delivering on the promise of a real-time open lakehouse architecture. ## Announcing AI for Citizens DevFeed: [Announcing AI for Citizens]() Original publisher: [Read original article]() Published: 2025-07-03T12:00:00Z Content type: news Language: en Sources: [Mistral AI Blog]() Topics: [AI Strategy](), [vendor lock-in](), [Frontier AI](), [AI Platform]() Tags: [ai](), [frontier-ai](), [mistral](), [privacy](), [public-sector](), [vendor-lock-in]() ### AI overview Mistral AI announces AI for Citizens, a collaborative initiative that helps states and public institutions strategically use AI to transform public services, encourage innovation, and maintain competitiveness. The initiative promotes greater control over AI and addresses risks associated with closed systems, vendor dependence, geopolitical constraints, and national requirements for safety, privacy, and data governance. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Why OpenAI chose ClickHouse for petabyte-scale observability DevFeed: [Why OpenAI chose ClickHouse for petabyte-scale observability]() Original publisher: [Read original article]() Author: ClickHouse Published: 2025-06-30T08:51:48Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [observability](), [OpenAI](), [telemetry](), [ChatGPT](), [Open Source](), [Traces](), [data]() Tags: [chatgpt](), [clickhouse](), [data](), [logs](), [observability](), [open-source](), [openai](), [telemetry](), [traces](), [vendor-lock-in]() ### AI overview OpenAI ingests petabytes of logs each day across model research, ChatGPT, and enterprise APIs. The article explains how ClickHouse supports fast, scalable observability for high-cardinality traces, ingestion spikes, real-time experiment analysis, and reliable log search without vendor lock-in. ### Source excerpt OpenAI ingests petabytes of logs a day, and ClickHouse is how they keep up. From billion-model experiments to viral ChatGPT spikes, see how they built observability for everything. ## Take Control of Your Photos - Self-Host Immich on Your Server DevFeed: [Take Control of Your Photos - Self-Host Immich on Your Server]() Original publisher: [Read original article]() Author: Techno Tim Published: 2025-06-15T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Docker](), [Self-hosted](), [Homelab](), [GPU](), [Open Source](), [Hardware]() Tags: [docker](), [gpu](), [home-server](), [how-to](), [install](), [nas](), [self-hosted](), [storage](), [vendor-lock-in]() ### AI overview A video tutorial explains how to install Immich, an open-source photo and video platform, on a home server using Docker. It covers NVIDIA GPU acceleration, mounting external NAS or network storage, configuring credentials and permissions, and starting the Immich stack. ### Source excerpt Protect your personal photos and videos by hosting them yourself. In this video, you'll learn how to install Immich, an open-source photo and video platform, on your own home server using Docker. Take control of your data with a fast, modern interface, GPU-accelerated features, and the ability to use your own NAS or network storage. 📺 Watch Video Info To to learn more about immich, check o... ## Let's Grow Xen Together! DevFeed: [Let's Grow Xen Together!]() Original publisher: [Read original article]() Author: Cody Zuschlag Published: 2025-03-18T15:01:27Z Content type: article Language: en Sources: [Blog - Xen Project]() Topics: [virtualization](), [Open Source](), [Security](), [Cloud](), [data centers](), [Critical Infrastructure](), [Internet of things]() Tags: [2025](), [cloud](), [colllaboration](), [community](), [contributors](), [critical-infrastructure](), [data-centers](), [developer](), [developers](), [ecosystem](), [edge-computing](), [embedded-systems](), [industrial](), [iot](), [open-source](), [performance](), [security](), [vendor-lock-in](), [virtualization]() ### AI overview This article introduces the Xen Project's new Community Manager and outlines plans to grow its contributor base, membership, and welcoming open-source ecosystem. It presents Xen as a secure, scalable, efficient, and cost-effective virtualization foundation for data centers, cloud and AI workloads, embedded systems, edge computing, automotive, industrial IoT, and other mission-critical applications. ### Source excerpt Xen is open, secure, and built for the future. As the new Community Manager, I'm focused on growing the Xen community, welcoming new contributors, and ensuring a thriving ecosystem. Let's build the future of virtualization together! ## Using Rails Views, Web Components, React, and Rails ViewComponents Together DevFeed: [Using Rails Views, Web Components, React, and Rails ViewComponents Together]() Original publisher: [Read original article]() Published: 2025-03-03T00:00:00Z Content type: opinion Language: en Sources: [Aha! Engineering Blog]() Topics: [Rails](), [React](), [Web Components](), [Server-side rendering](), [Front end](), [vendor lock-in]() Tags: [components](), [front-end](), [opinion](), [rails](), [react](), [server-side-rendering](), [vendor-lock-in]() ### AI overview The article argues that Rails views, web components, React, and Rails ViewComponents are not mutually exclusive. It explains that each approach addresses different problems and can be combined thoughtfully, including server rendering for simpler data-display features and web components for avoiding vendor lock-in. ### Source excerpt How many times have you heard or read statements like these in tech discussions?"Everything needs to be a single-page app these days. Server-rendered templates are holding you back.""Web components are the future. Why tie yourself to any framework?" ## Neon Auth is Here: Get Authentication in a Couple of Clicks DevFeed: [Neon Auth is Here: Get Authentication in a Couple of Clicks]() Original publisher: [Read original article]() Author: Brian Holt Published: 2025-02-20T17:35:57Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [Authentication](), [Database](), [Provisioning](), [migration](), [Software as a service](), [Open Source]() Tags: [authentication](), [company](), [customization](), [database](), [migration](), [open-source](), [provisioning](), [saas](), [sync](), [vendor-lock-in]() ### AI overview Neon announces Neon Auth, a fully managed authentication solution integrated with the Neon platform. It provisions Stack Auth from the Neon console and automatically synchronizes user profiles with the database, while supporting ownership transfer, manual setup, customization, and migration away from Neon. ### Source excerpt We're excited to announce Neon Auth, a fully managed authentication solution tightly integrated into the Neon platform. It now takes seconds to provision an auth solution directly from the Neon console; once set up, your user profiles automatically sync to your database. The best... ## Planting New Platform Roots in Cloud Native with Fir DevFeed: [Planting New Platform Roots in Cloud Native with Fir]() Original publisher: [Read original article]() Author: Terence Lee Published: 2024-12-02T14:15:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Cloud Native Ecosystem](), [Buildpacks](), [Kubernetes](), [Cloud]() Tags: [buildpacks](), [cloud-infrastructure](), [cloud-native](), [developer-tools](), [fir](), [heroku](), [kubernetes](), [news](), [nextgen](), [open-source](), [opentelemetry](), [platform](), [scalability](), [vendor-lock-in]() ### AI overview Heroku introduces Fir, a new technology stack built on cloud-native technologies and open source standards. The article describes its use of OCI images, Cloud Native Buildpacks, OpenTelemetry, and Kubernetes to support portability, interoperability, scalability, and developer experience. ### Source excerpt Cloud platforms have come a long way since Heroku first set out to empower developers. Today's cloud native development demands even greater flexibility, openness, and scalability. A fun fact about Heroku is that we use trees to denote the generation of the platform technology stack (aka version). In the tradition of Aspen, Bamboo, and Cedar, [...] The post Planting New Platform Roots in Cloud Native with Fir appeared first on Heroku. ## Planning Your PostgreSQL Migration: Best Practices and Key Considerations DevFeed: [Planning Your PostgreSQL Migration: Best Practices and Key Considerations]() Original publisher: [Read original article]() Author: Ken W. Alger Published: 2024-11-19T19:40:49Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [migration](), [PostgreSQL](), [Database Migration](), [Cloud](), [vendor lock-in](), [interoperability]() Tags: [cli](), [cloud](), [compatibility](), [configuration](), [database](), [database-migration](), [developer-tools](), [heroku-postgres](), [interoperability](), [migration](), [postgresql](), [sql](), [uncategorized](), [vendor-lock-in]() ### AI overview This guide explains how to plan a PostgreSQL migration between cloud providers. It covers evaluating the current database setup, checking PostgreSQL version and extension compatibility, and documenting configuration settings before migration. ### Source excerpt Your organization may have many reasons to move a cloud service from one provider to another. Maybe you've found a better performance-versus-cost balance elsewhere. Maybe you're trying to avoid vendor lock-in. Whatever your reasons, the convenience and general interoperability of cloud services today put you in the driver's seat. You get to piece together the [...] The post Planning Your PostgreSQL Migration: Best Practices and Key Considerations appeared first on Heroku. ## Free the data: Why US federal agencies should standardize on OpenTelemetry DevFeed: [Free the data: Why US federal agencies should standardize on OpenTelemetry]() Original publisher: [Read original article]() Author: Bill Wright Published: 2024-06-26T00:00:00Z Content type: opinion Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [OpenTelemetry](), [telemetry](), [interoperability](), [vendor lock-in](), [Open Source](), [data-processing](), [Monitoring](), [Cloud Native Ecosystem]() Tags: [collection](), [cost-savings](), [government](), [interoperability](), [migrations](), [observability](), [open](), [opentelemetry](), [opentelemetry-data-ingestion-open-source-standards-government](), [public-sector-government](), [standard](), [standards](), [systems](), [telemetry](), [universal-profiling-logs-metrics](), [us](), [vendor-lock-in]() ### AI overview The article argues that US federal agencies should standardize on OpenTelemetry, an open-source observability framework and CNCF project. It presents unified collection of traces, metrics, and logs as a way to reduce vendor lock-in and costs, improve interoperability and collaboration, and provide adaptable monitoring across government applications and infrastructure. ### Source excerpt Adopting OpenTelemetry standards can enhance the government's ability to manage and analyze telemetry data across diverse systems - ensuring consistent and reliable data collection and leading to better decision-making and improved service delivery. ## Data Center Fabric Designs: Size Matters DevFeed: [Data Center Fabric Designs: Size Matters]() Original publisher: [Read original article]() Published: 2024-03-14T07:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [data centers](), [Architecture & Design](), [Networks](), [vendor lock-in](), [Streaming]() Tags: [architecture-design](), [data-center](), [design](), [evpn](), [fabric](), [networks](), [streaming](), [vendor-lock-in]() ### AI overview The article argues that the appropriate data center fabric design depends on network size and operational complexity. Mixing vendors may help large streaming services avoid vendor lock-in, reduce prices, and address supply-chain issues, but it is usually impractical for enterprise data centers because the operational costs of multiple operating systems, support centers, and tooling can outweigh acquisition savings. ### Source excerpt The "should we use the same vendor for fabric spines and leaves?" discussion triggered the expected counterexamples. Here's one: I actually have worked with a few orgs that mix vendors at both spine and leaf layer. Can't take names but they run fairly large streaming services. To me it seems like a play to avoid vendor lock-in, drive price points down and be in front of supply chain issues. As always, one has to keep two things in mind: Read more ... ## The PaaS Dilemma DevFeed: [The PaaS Dilemma]() Original publisher: [Read original article]() Author: Dominic Black Published: 2023-08-03T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [paas and iaas](), [vendor lock-in](), [Open Source](), [hosting](), [Amazon Web Services](), [fly]() Tags: [aws](), [gcp](), [hosting](), [open-source](), [platform-as-a-service-paas](), [vendor-lock-in]() ### AI overview This opinion article discusses how Platform-as-a-Service products create customer trust and vendor lock-in concerns. It compares invisible integrations, illustrated by Fly.io, with deeper integrations such as AWS APIs, and presents an open-source approach as Encore's response to these challenges. ### Source excerpt Overcoming trust issues and vendor lock-in through an open-source approach [Next page]()