Mitigating Cloud Dependency with Local-First Software and Open Protocols
This article discusses strategies for mitigating Europe's dependency on major US cloud providers by advocating for technological sovereignty through multi-cloud commoditization, decentralized social media protocols, and local-first software. It highlights how these approaches shift power from centralized providers back to users and enable greater flexibility and resilience in system design. Key themes include open standards, credible exit strategies, and designing systems where local data primacy reduces reliance on constant cloud connectivity.
Read original on InfoQ ArchitectureThe article presents a critical examination of the concentrated market share of major US cloud providers in Europe, emphasizing the inherent risks of such dependency, including potential service lockouts due to geopolitical events or sanctions. Martin Kleppmann, author of 'Designing Data-Intensive Applications', advocates for architectural choices that promote 'technological sovereignty' by reducing reliance on single providers and empowering users.
Strategies for Technological Sovereignty
Kleppmann proposes three key technological directions to mitigate cloud dependency and foster technological sovereignty:
- Multi-cloud and Commoditization: The ability to switch providers for backend services is paramount. This is achieved through de facto standards like the S3 API for object stores, Kubernetes for deployment, Kafka protocol for streaming, and PostgreSQL wire protocol for databases. While this increases operational complexity and may limit advanced features, it ensures vendor interchangeability, similar to how screw threads were standardized during the Industrial Revolution.
- The AT Protocol and Bluesky: For social media, the AT Protocol exemplifies a 'credible exit' strategy. Users can switch providers without losing their data (username, social graph, posts) because data resides in personal repositories hosted on Personal Data Servers (PDSs), allowing anyone to run a PDS. This decentralized approach, with a centralized but cryptographically protected user directory, ensures user data ownership and platform independence.
- Local-First Software: This paradigm prioritizes the user's local copy of data, reducing cloud services to merely sync and backup functions. Inspired by CRDTs (Conflict-Free Replicated Data Types) and projects like Automerge, local-first software enables features like real-time collaboration with offline capabilities, version control, and peer-to-peer sync, significantly minimizing the role of centralized servers. This approach is well-suited for productivity tools but not for systems managing physical resources (e.g., bank accounts) requiring a single authoritative source.
Design Principle: Credible Exit
Designing for 'credible exit' means architecting systems such that users can easily migrate their data and identity between competing service providers without significant loss or friction. This often involves open standards, decentralized data storage, and portable data formats, ensuring users are not locked into a single vendor due to the cost of switching.
Trade-offs and Considerations
While these strategies offer significant benefits in terms of sovereignty and resilience, they come with trade-offs. Commoditization can lead to increased cost and operational complexity, as systems might be limited to 'lowest-common-denominator' features. Decentralized systems like those using the AT Protocol or local-first software introduce challenges in managing distributed state, ensuring data consistency, and simplifying user experience in a fragmented ecosystem. The core takeaway is that engineering choices directly influence the distribution of power between users and service providers.