# Multitenancy A software architecture approach for serving multiple customers, or tenants, through a shared solution with configurable resource isolation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build a multi-user Claude Agent SDK app that acts as each of your users DevFeed: [Build a multi-user Claude Agent SDK app that acts as each of your users]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-24T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Claude](), [SDKs](), [Multitenancy](), [Next.js](), [Model Context Protocol](), [anthropic]() Tags: [agent](), [build](), [claude](), [how-to](), [mcp](), [multi-tenancy](), [next-js](), [sdk]() ### AI overview This tutorial explains how to build a multi-user Claude Agent SDK application whose tool calls run with the signed-in user's identity. It recommends constructing the tool surface per request, capturing the acting user in a closure, and exposing no tool parameter that lets the model choose another user. ### Source excerpt Follow the official Agent SDK examples and every user's agent runs on one shared token, which is usually yours. Here is how to bind each tool call to the signed-in user instead, using AuthKit and Pipes relay. ## Build an EKS Environment Factory with Pulumi and vCluster DevFeed: [Build an EKS Environment Factory with Pulumi and vCluster]() Original publisher: [Read original article]() Author: Pablo Seibelt Published: 2026-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Amazon EKS](), [Multitenancy](), [Kubernetes](), [Provisioning](), [Architecture & Design](), [Amazon Web Services](), [CI/CD]() Tags: [amazon-eks](), [architecture](), [aws](), [ci-cd](), [infrastructure](), [kubernetes](), [multi-tenancy](), [platform-engineering](), [provisioning](), [pulumi](), [tutorials]() ### AI overview A tutorial shows how to build an ephemeral Kubernetes environment factory with Pulumi, Amazon EKS Auto Mode, and vCluster. It uses a shared host cluster with virtual tenant clusters to reduce environment sprawl, provisioning delays, and operational overhead while preserving tenant isolation controls. ### Source excerpt AWS reports in an AWS Architecture Blog case study that Deloitte's move to a virtual cluster model on Amazon EKS resulted in 89% faster testing environment provisioning. By consolidating dozens of disparate clusters into a single host cluster with over 50 vCluster instances, the case study says Deloitte saved about 500 QA hours per year. This "Environment Factory" pattern allows platform teams to provide isolated, ephemeral Kubernetes environments on demand without the cost or lag of full cluster provisioning. This post adapts that general architecture with Pulumi to orchestrate Amazon EKS Auto Mode and vCluster. The problem: environment sprawl and provisioning lag Traditional development workflows often rely on one full EKS cluster per developer or feature branch. While this provides strong isolation, it introduces major pain points. Provisioning a full cluster can take 15 minutes or more, which slows down CI/CD pipelines. Managing dozens of clusters also leads to high costs and significant operational overhead. Platform teams need a "soft multi-tenancy" model. This model should feel like a dedicated cluster to the developer but run on shared infrastructure to keep costs low and startup times fast. Architecture overview: the host and the tenants The environment factory architecture consists of two main layers. Host cluster: A single, reliable EKS cluster managed with EKS Auto Mode. This cluster provides the underlying compute, networking, and storage. Tenant environments: Virtual clusters (vCluster) running as pods within host namespaces. According to the vCluster architecture, the virtual control plane handles API requests while a syncer maps virtual resources to the host cluster. This separation allows tenants to manage their own CRDs, namespaces, and RBAC while platform teams use quotas, NetworkPolicies, pod security, IAM boundaries, and node isolation controls to protect the host and other tenants. Implementation: the EKS Auto Mode host EKS Auto Mode simplifies ## Secure Multitenancy with OpenShift and Isovalent Networking for Kubernetes DevFeed: [Secure Multitenancy with OpenShift and Isovalent Networking for Kubernetes]() Original publisher: [Read original article]() Author: Christian Hernandez Published: 2026-04-30T07:01:05Z Content type: article Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [Multitenancy](), [networking](), [Kubernetes]() Tags: [blog](), [isovalent](), [kubernetes](), [multitenancy](), [networking]() ### AI overview The article explores how Isovalent Networking for Kubernetes fits into OpenShift's multitenancy model. ### Source excerpt OpenShift has long treated multitenancy as a core platform concern and in this blog we explore how Isovalent Networking for Kubernetes fits perfectly in this model! ## Atoms is Out, a Multi-Agent AI Team that Builds Full-Stack Apps for You DevFeed: [Atoms is Out, a Multi-Agent AI Team that Builds Full-Stack Apps for You]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2026-01-13T17:48:26Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Artificial Intelligence](), [App](), [Multitenancy](), [Per-user Database](), [Databases](), [Back end](), [Front end](), [Automation](), [Deployment](), [Software as a service](), [Iris](), [AI research agents]() Tags: [agent](), [ai](), [ai-agents](), [apps](), [architecture](), [automation](), [backend](), [case-studies](), [code](), [data](), [database](), [deployment](), [infrastructure](), [product](), [product-development](), [saas](), [scale](), [software]() ### AI overview Atoms is a multi-agent AI platform that builds full-stack software products from a user prompt. Specialized agents handle research, product requirements, architecture, engineering, data analysis, testing, and deployment. Its multi-tenant architecture gives each user app a dedicated Postgres database provisioned dynamically through Neon. ### Source excerpt "We chose Neon as our backend because of scale, cost-efficiency, and superior developer and user experience, all critical for Atoms' multi-tenant architecture. Each user app needs its own dedicated database, and Neon lets us spin up Postgres instances dynamically while only payin... ## Web Analytics Architecture for Multitenancy and AI DevFeed: [Web Analytics Architecture for Multitenancy and AI]() Original publisher: [Read original article]() Author: Víctor Ramírez, Alberto Romeu Published: 2025-08-13T14:00:00Z Content type: tutorial Language: en Sources: [Tinybird]() Topics: [Web](), [Multitenancy](), [Artificial Intelligence]() Tags: [ai](), [analytics](), [architecture](), [i-built-this](), [multitenancy](), [web]() ### AI overview The article describes the architecture of a web analytics platform that uses multitenancy and AI to serve thousands of customers from one platform. ### Source excerpt Web analytics with multitenancy and AI serves thousands of customers from one platform. Here's the architecture behind it. ## Turso Cloud Goes Diskless: How We Built a Fully S3-Based Database Architecture DevFeed: [Turso Cloud Goes Diskless: How We Built a Fully S3-Based Database Architecture]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2025-04-07T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Turso](), [Amazon S3](), [Architecture & Design](), [Multitenancy](), [Cloud](), [SQLite](), [Amazon Web Services](), [Scalability](), [Kubernetes]() Tags: [architecture](), [article](), [aws](), [cloud](), [compliance](), [kubernetes](), [s3](), [scalability](), [sqlite](), [storage](), [technology](), [turso]() ### AI overview Turso Cloud describes a diskless transactional database architecture that runs entirely on S3, including AWS S3 Express One Zone. The design removes local disks and simplifies Bring Your Own Cloud deployments while addressing scalability, reliability, multi-tenancy, compliance, and latency trade-offs. ### Source excerpt How Turso Cloud runs a transactional SQLite database fully on S3 and S3 Express, removing local disks and unlocking Bring Your Own Cloud deployments. ## Multi-Tenant E-Commerce Architecture with Turso DevFeed: [Multi-Tenant E-Commerce Architecture with Turso]() Original publisher: [Read original article]() Author: Jamie Barton Published: 2024-11-26T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Architecture & Design](), [Multitenancy](), [Turso](), [Scalability](), [Database](), [Drizzle](), [Vercel](), [stripe](), [configuration](), [.env](), [Deployment]() Tags: [architecture](), [database](), [deployment](), [drizzle](), [e-commerce](), [environment-variables](), [scalability](), [schema](), [stripe](), [turso](), [vercel]() ### AI overview This article presents a multi-tenant e-commerce architecture that uses one codebase for multiple storefronts. Store-specific themes and settings are controlled through environment variables, while each store uses an isolated database and deployment. The approach aims to simplify development and provide a practical balance between tenant separation and scalability, using Turso, Drizzle, Vercel, and dedicated Stripe accounts. ### Source excerpt Create multiple storefronts using a single codebase while maintaining separation of concerns and scalability. ## Databases will be free DevFeed: [Databases will be free]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2024-11-19T00:00:00Z Content type: opinion Language: en Sources: [Turso Blog]() Topics: [Databases](), [Multitenancy](), [Turso](), [Provisioning](), [Artificial Intelligence](), [DRIVE]() Tags: [agents](), [ai-agents](), [centralization](), [databases](), [multitenancy](), [provisioning](), [turso]() ### AI overview The article argues that database costs will eventually fall close to zero, enabling plentiful individual and ephemeral databases. It connects this shift to a microdatabase model, AI agents requiring disposable databases for agentic memory, and Turso's efforts toward massive multitenancy and lower-cost provisioning. ### Source excerpt In the near future, databases will be free and plentiful. What does that change for you? ## Analytics for Per-User Database Architecture DevFeed: [Analytics for Per-User Database Architecture]() Original publisher: [Read original article]() Author: Jamie Barton Published: 2024-11-18T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Per-user Database](), [Multitenancy](), [Turso](), [SQLite](), [Platform API](), [Data Management](), [Architecture & Design](), [Software as a service](), [data-architecture](), [Databases]() Tags: [architecture](), [data-management](), [database](), [databases](), [etl](), [metrics](), [monitor](), [per-user-database](), [platform-api](), [reporting](), [saas](), [sqlite](), [turso]() ### AI overview This article explains how to aggregate analytics from a per-user or per-tenant Turso database architecture. It describes using an ETL script to query individual SQLite databases, collect metrics such as orders, revenue, shopping carts, and products, and store the results in a central database for reporting and platform monitoring. ### Source excerpt Aggregating Multi-Tenant Databases for Analytics and Reporting ## Is Postgres RLS for Everything and Everyone? DevFeed: [Is Postgres RLS for Everything and Everyone?]() Original publisher: [Read original article]() Author: David Gomes Published: 2024-11-15T17:32:58Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Authorization](), [Multitenancy](), [Per-user Database](), [SQL](), [Security](), [Drizzle](), [Object-relational mapping](), [Architecture & Design]() Tags: [authorization](), [blog-post](), [database](), [drizzle](), [multitenancy](), [orm](), [postgres](), [security](), [sql](), [testing]() ### AI overview The article examines whether PostgreSQL Row-Level Security (RLS) should express an application's entire authorization model. It recommends a project-per-user pattern for multitenancy when possible, while describing RLS as a way to prevent cross-tenant access in a shared database. It discusses RLS's dense syntax, recursion errors, policy behavior, security settings, optimizer considerations, and testing difficulties, and notes that Drizzle ORM can simplify some TypeScript usage. ### Source excerpt In Neon, we recommend using a project-per-user pattern for multitenancy whenever possible. If this doesn't work for you and you're placing all your tenants within a single Postgres database, you should at least use RLS to prevent cross-tenant access--but expressing your entire aut... ## Adaptive Computer chooses Turso ephemeral databases to power AI agents that build and modify software DevFeed: [Adaptive Computer chooses Turso ephemeral databases to power AI agents that build and modify software]() Original publisher: [Read original article]() Author: Mike Soylu Published: 2024-10-21T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Turso](), [AI Agent](), [Platform API](), [Multitenancy](), [SQLite]() Tags: [ai-agents](), [multitenancy](), [platform-api](), [sqlite](), [turso]() ### AI overview Adaptive Computer describes using Turso to provision and branch databases for AI-agent changes to applications, validate those changes, and roll them back when needed. The company says it had 40,000 Turso databases in September while still in alpha. ### Source excerpt How Adaptive Computer uses Turso multitenancy to create tens of thousands of databases that power AI agent actions ## How Drizzle Leverages Turso for Its Products and Services DevFeed: [How Drizzle Leverages Turso for Its Products and Services]() Original publisher: [Read original article]() Author: Aleksandr Blokh Published: 2024-10-17T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Drizzle](), [Turso](), [Object-relational mapping](), [SQLite](), [TypeScript](), [Multitenancy](), [Replication](), [Latency]() Tags: [drizzle](), [latency](), [multitenancy](), [orm](), [performance](), [replication](), [sqlite](), [turso](), [typescript]() ### AI overview Drizzle explains how it uses Turso in production for data-centric applications, including Drizzle Studio themes, web analytics, an internal analytical back office, and a game. The article highlights Turso's SQLite foundation, schema capabilities, vector support, transparent pricing, replication, recovery, multi-region support, and scalability. ### Source excerpt Drizzle ORM is a longtime user of Turso to power various products and services it offers. Here's how they use it. ## Working with Clerk and per-user databases DevFeed: [Working with Clerk and per-user databases]() Original publisher: [Read original article]() Author: Jamie Barton Published: 2024-05-07T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [Multitenancy](), [Turso](), [Authentication](), [Database](), [React](), [Next.js]() Tags: [apps](), [architecture](), [authentication](), [building](), [databases](), [framework](), [how-to](), [learn](), [multi-tenancy](), [next-js](), [platform-api](), [react](), [sqlite](), [turso]() ### AI overview A tutorial on creating per-user databases for a multi-tenant application with Turso's Multi-DB Schemas and Clerk. It explains using a parent database as a template, propagating schema changes to child databases, and creating user databases through Clerk webhooks. ### Source excerpt Learn how to create per-user databases in a multi-tenant architecture using Turso's Multi-DB Schemas feature and Clerk for user authentication and management. ## How OpusFlow achieves tenant isolation in Postgres without managing servers DevFeed: [How OpusFlow achieves tenant isolation in Postgres without managing servers]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2024-02-22T17:28:50Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Per-user Database](), [tenant data protection](), [Amazon RDS](), [Multitenancy](), [Encryption](), [DevOps](), [Databases]() Tags: [amazon-rds](), [architecture](), [business](), [case-studies](), [customers](), [data](), [database](), [devops](), [encryption](), [energy](), [postgres]() ### AI overview The article describes how OpusFlow, an ERP tool for sustainable energy installers, addresses sensitive European customer data through a one-database-per-customer architecture in Postgres. It explains that this design improves tenant isolation, supports separate encryption keys, independent scaling, customer-specific restores, and separate upgrade schedules. The article contrasts this approach with Amazon RDS deployments, which either allow resource contention in a shared instance or create substantial operational and cost overhead when each database uses a separate instance. ### Source excerpt "Our customers require their data to live in an isolated database, but implementing this in RDS was cumbersome and expensive. We switched over to Neon to reduce costs and operational overhead" Joey Teunissen, CTO at OpusFlow The demand for solar panels and sustainable energy inst... ## What's New in Apache Pulsar 3.2.0 DevFeed: [What's New in Apache Pulsar 3.2.0]() Original publisher: [Read original article]() Author: Julien Jakubowski Published: 2024-02-12T00:00:00Z Content type: release Language: en Sources: [Apache Pulsar Blog]() Topics: [Apache Pulsar](), [Messaging](), [Multitenancy](), [WebSocket](), [Security](), [Encryption](), [Refactoring]() Tags: [apache](), [collaboration](), [contributors](), [features](), [messaging](), [multi-tenancy](), [refactoring](), [release](), [security](), [websocket]() ### AI overview Apache Pulsar 3.2 is a feature release with more than 180 improvements, optimizations, and fixes across the broker, Pulsar IO, Pulsar Functions, and CLI. It adds rate-limiting refactoring for capacity management and QoS, changes topic compaction to delete null-key messages by default, introduces WebSocket API updates, improves security for connector secrets, and enhances the CLI user experience. ### Source excerpt The Apache Pulsar community is thrilled to announce the launch of Apache Pulsar 3.2, a new feature release! This achievement is the result of a significant community collaboration, involving 57 contributors who made over 88 commits to add new features and fix bugs. Our heartfelt thanks go out to every contributor for their invaluable work! ## How Apple built iCloud to store billions of databases DevFeed: [How Apple built iCloud to store billions of databases]() Original publisher: [Read original article]() Author: Engineer's Codex Published: 2024-01-14T21:53:05Z Content type: article Language: en Sources: [Engineer's Codex]() Topics: [Apache Cassandra](), [Database](), [Multitenancy](), [Cloud](), [NoSQL](), [Architecture & Design](), [Scalability]() Tags: [architecture](), [cassandra](), [cloud](), [database](), [nosql](), [scalability](), [separate]() ### AI overview This article examines how Apple built iCloud and CloudKit using FoundationDB and Cassandra. It discusses the systems' extreme multi-tenant architecture and engineering choices such as asynchronous processing, stateless design, resource isolation, and layered abstractions to support scalability, reliability, availability, and developer experience. ### Source excerpt Apple uses Cassandra and FoundationDB for CloudKit, their cloud backend service. We take a look into how exactly each is used within their cloud and the problems they've solved. ## Measuring uptime for Neon's multi-tenant architecture DevFeed: [Measuring uptime for Neon's multi-tenant architecture]() Original publisher: [Read original article]() Author: Stas Kelvich Published: 2023-12-08T21:49:03Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Multitenancy](), [incident](), [Monitoring](), [Incident response](), [systems](), [Cloud](), [Databases]() Tags: [architecture](), [cloud-native](), [community](), [databases](), [distributed](), [distributed-system](), [engineering](), [incident](), [incident-response](), [monitoring](), [monitoring-alerting](), [platform](), [postgres](), [storage](), [uptime]() ### AI overview Neon explains why it removed the default uptime percentage from its status page and is exploring project-level uptime ranges to better represent service health across its multi-tenant distributed system. ### Source excerpt In the past two months, we've had several incidents that affected different aspects of our service. We've been transparent about them, and we made sure that each major one included details on what happened, the size of the impact, and what we're doing to prevent it from happening... ## Surprising Scalability of Multitenancy DevFeed: [Surprising Scalability of Multitenancy]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2023-03-23T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Multitenancy](), [Scalability](), [Amazon S3](), [Cloud]() Tags: [architecture](), [cloud](), [cost](), [economics](), [multitenancy](), [performance](), [s3](), [scalability](), [storage](), [systems]() ### AI overview The article explains how multi-tenancy improves the economics and scalability of cloud systems by reducing the overall peak-to-average traffic ratio. Using Amazon S3 as an example, it describes how distributing customer workloads across many storage devices can support high individual workload peaks without making the overall system disproportionately expensive. ### Source excerpt Surprising Scalability of Multitenancy When most folks talk about the economics of cloud systems, their focus is on automatically scaling for long-term seasonality: changes on the order of days (fewer people buy things at night), weeks (fewer people visit the resort on weekdays), seasons, and holidays. Scaling for this kind of seasonality is useful and important, but there's another factor that can be even more important and is often overlooked: short-term peak-to-average. Roughly speaking, the cost of a system scales with its (short-term1) peak traffic, but for most applications the value the system generates scales with the (long-term) average traffic. The gap between "paying for peak" and "earning on average" is critical to understand how the economics of large-scale cloud systems differ from traditional single-tenant systems. Why is it important? It's important because multi-tenancy (i.e. running a lot of different workloads on the same system) very effectively reduces the peak-to-average ratio that the overall system sees. This is highly beneficial for two reasons. The first-order reason is that it improves the economics of the underlying system, by bringing costs (proportional to peak) closer to value (proportional to average). The second-order benefit, and the one that is most directly beneficial to cloud customers, is that it allows individual workloads to have higher peaks without breaking the economics of the system. Most people would call that scalability. Example 1: S3 Earlier this month, Andy Warfield from the S3 team did a really fun talk at OSDI'23 about his experiences working on S3. There's a lot of gold in his talk, but there's one point he made that I think is super important, and worth diving deeper into: heat management and multi-tenancy. Here's the start of the relevant bit on heat2 management: Andy makes a lot of interesting point here, but the key one has got to do with the difference between the per object heat distribution, the per aggregat ## Supabase Realtime, with Multiplayer Features DevFeed: [Supabase Realtime, with Multiplayer Features]() Original publisher: [Read original article]() Author: Wen Bo Xie Published: 2022-04-01T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [WebSocket](), [Multitenancy](), [distributed-systems](), [Concurrency](), [Databases](), [Streaming](), [Elixir](), [phoenix]() Tags: [apps](), [architecture](), [concurrency](), [databases](), [developers](), [elixir](), [extension](), [features](), [multi-tenancy](), [phoenix](), [postgresql](), [streaming]() ### AI overview Supabase announces a new version of Realtime that adds multiplayer capabilities alongside existing PostgreSQL change streaming. The release introduces multi-tenancy, distributed clusters, presence, broadcast messaging, and a more extensible WebSocket architecture for games and collaborative applications. ### Source excerpt Today we're announced Realtime, with multiplayer features. Realtime enables broadcast, presence, and listening to database changes delivered over WebSockets. ## Secure Apache Airflow Using Customer Security Manager DevFeed: [Secure Apache Airflow Using Customer Security Manager]() Original publisher: [Read original article]() Author: Yifei Sun Published: 2022-01-19T20:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [airflow](), [Security](), [Access Control](), [Orchestration](), [Multitenancy]() Tags: [access-control](), [airflow](), [apache](), [authz](), [data-science](), [http](), [multi-tenancy](), [security](), [web]() ### AI overview This article describes Square's security requirements for running Apache Airflow in a multi-tenant environment. It explains using a human proxy to pass user identities and capabilities to the Airflow web console through HTTP headers, supporting automatic login and role- and DAG-level access control without offline permission synchronization. ### Source excerpt Leverage a human proxy to auto log users in airflow web console ## When Language Runtime Scheduling Fails in Multi-Tenant Services DevFeed: [When Language Runtime Scheduling Fails in Multi-Tenant Services]() Original publisher: [Read original article]() Author: sasha@goteleport.com (Alexander Klizhentas) Published: 2020-12-03T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Programming](), [Concurrency](), [Go Language](), [Multitenancy](), [Software as a service]() Tags: [concurrency](), [go](), [goroutines](), [memory](), [multi-tenancy](), [outage](), [performance](), [pitfalls]() ### AI overview The article examines how language runtime scheduling can affect multi-tenant services. It uses Go examples to explain concurrent network workloads and shows how CPU-intensive work can let one tenant consume resources and degrade performance for others. ### Source excerpt Explore edge-cases in which programming language runtimes fail to provide fair resource scheduling that leads to outages. ## How to Introduce Composite Primary Keys in Rails DevFeed: [How to Introduce Composite Primary Keys in Rails]() Original publisher: [Read original article]() Author: John Arthorne Published: 2020-10-29T19:00:36Z Content type: tutorial Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [Databases](), [MySQL](), [Multitenancy](), [Scalability](), [Architecture & Design]() Tags: [architecture](), [code](), [database](), [how-to](), [mysql](), [performance](), [rails](), [scalability](), [shopify]() ### AI overview This Shopify engineering article explains how composite primary keys can improve data locality and query performance in a Rails application with a multi-tenant database architecture. It discusses how auto-incrementing primary keys interleave records from different shops, while queries commonly access one shop at a time, and introduces the relevant MySQL InnoDB storage concepts, including B+ trees and pages. ### Source excerpt One line of code can 5x your Rails application performance. What if you could make a small change to your database design that would unlock massively more efficient data access? At Shopify, we dusted off some old database principles and did exactly that with the primary Rails application. ## Hard Multi-Tenancy in Kubernetes DevFeed: [Hard Multi-Tenancy in Kubernetes]() Original publisher: [Read original article]() Published: 2018-05-18T19:17:58Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [Kubernetes](), [Multitenancy](), [Security](), [Architecture & Design](), [Software as a service]() Tags: [api](), [kubernetes](), [multi-tenancy](), [security](), [vulnerabilities]() ### AI overview This article examines hard multi-tenancy in Kubernetes, where tenants sharing a cluster are assumed not to trust one another. It argues that Kubernetes namespace isolation is not yet a sufficient security boundary and discusses the need for layered security, including isolation of the Kubernetes API. ### Source excerpt EDIT: See my post on a design doc for a multi-tenant orchestrator instead. I wrote this when an internal requirement was to use Kubernetes but I do not personally think you should use Kubernetes for this use case. Kubernetes is the new kernel. We can refer to it as a "cluster kernel" versus the typical operating system kernel. This means a lot of great things for users trying to deploy applications. It also leads to a lot of the same challenges we have already faced with operating system kernels. One of which being privilege isolation. In Kubernetes, we refer to this as multi-tenancy, or the dream of being able to isolate tenants of a cluster. The models for multi-tenancy have been discussed at length in the community's multi-tenancy working group. NOTE: to view most of these Google docs you need to be a member of the kubernetes-wg-multitenancy Google group. There have also been some proposals offered to solve each model. The current model of tenancy in Kubernetes assumes the cluster is the security boundary. You can build a SaaS on top of Kubernetes but you need to bring your own trusted API and not just use the Kubernetes API. Of course, with that comes a lot of considerations you must also think about when building your cluster securely for a SaaS even. The model I am going to be focusing on for this post is "hard multi-tenancy." This implies that tenants do not trust each other and are assumed to be actively malicious and untrustworthy. Hard multi-tenancy means multiple tenants in the same cluster should not have access to anything from other tenants. In this model, the goal is to have the security boundary be the Kubernetes namespace object. The hard multi-tenancy model has not been solved yet, but there have been a few proposals. All systems have weaknesses and nothing is perfect. With a system as complex and large as Kubernetes it is hard to trust the entire system to not be vulnerable. In this regard and in the regard of the existing proposals, one single ex