#Multitenant — Bluesky Posts

1 month ago

📝 New blog post
"3 Pitfalls of Multi-Portal Authentication with Keycloak [Part 5]"
ko-chan.github.io/saru-blog/posts-en/saru-...
#Keycloak #Authentication #Nextjs #Authjs #Multitenant

1 0 0 0

@markjackmilian.bsky.social

1 month ago

📝 ブログ記事を投稿しました
"Keycloakマルチポータル認証の3つの落とし穴 [第5回]"
zenn.dev/ko_chan/articles/saru-ke...
#Keycloak #Authentication #Nextjs #Authjs #Multitenant

2 0 0 0

Mark Jack

1 month ago

Just a moment...

Explore the benefits & implementation of multi-tenant architecture in .NET applications. Discover scalability strategies and best practices. Enhance your software's efficiency and performance! #DotNet #MultiTenant

0 0 0 0

2 months ago

📝 New blog post
"PostgreSQL RLS for Multi-Tenant Isolation: Protecting 4-Tier Data as a Solo Developer [Part 4]"
ko-chan.github.io/saru-blog/posts-en/saru-...
#PostgreSQL #RLS #Multitenant #Go #Security

1 0 0 0

2 months ago

📝 ブログ記事を投稿しました
"1人では保守できない複雑さに自動化で挑む：マルチテナントSaaS開発記【第1回】"
zenn.dev/ko_chan/articles/saru-mu...
#自動化 #ソロ開発 #Multitenant #Claude Code #E2Eテスト

0 0 0 0

Multitenant versus nonCDB Architektur – Database Blog

2 months ago

📝 New blog post
"Tackling Unmaintainable Complexity with Automation: Building a Multi-Tenant SaaS Solo - Part 1"
ko-chan.github.io/saru-blog/posts-en/saru-...
#automation #solodevelopment #multitenant #claudecode #e2etesting

2 0 0 0

Chris Pfundtner

@cpfundtner.bsky.social

3 months ago

#Oracle #Multitenant versus #nonCDB Architektur - kann man mit Multitenant wirklich so viele Resourcen und Aufwände sparen? Meine Erfahrungen dazu im neuesten Blog.
@oracleace.bsky.social @doagev.bsky.social

www.database-blog.at/2025/12/16/m...

0 0 0 0

Mauricio Cassemiro

@mauriciocassemiro.bsky.social

3 months ago

#microsoftentra #entraid #microsoftidentity #multitenant #sincronização #segurança #governança #ti #transformaçãodigital #produtividade #crosstenantsecuritygroupsynchronization #cloudsecurity… | Mauri... 🔄👨‍👦‍👦🛡️𝗔 𝗦𝗶𝗻𝗰𝗿𝗼𝗻𝗶𝘇𝗮çã𝗼 𝗱𝗲 𝗚𝗿𝘂𝗽𝗼𝘀 𝗱𝗲 𝗦𝗲𝗴𝘂𝗿𝗮𝗻ç𝗮 𝗲𝗻𝘁𝗿𝗲 𝗧𝗲𝗻𝗮𝗻𝘁𝘀 𝗲𝘀𝘁á 𝗰𝗵𝗲𝗴𝗮𝗻𝗱𝗼 𝗮𝗼 𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗘𝗻𝘁𝗿𝗮! Por anos, gerenciar grupos de segurança entre tenants exigiu scripts, jobs de sincronização e soluções f...

🔄👨‍👦‍👦🛡️𝗔 𝗦𝗶𝗻𝗰𝗿𝗼𝗻𝗶𝘇𝗮çã𝗼 𝗱𝗲 𝗚𝗿𝘂𝗽𝗼𝘀 𝗱𝗲 𝗦𝗲𝗴𝘂𝗿𝗮𝗻ç𝗮 𝗲𝗻𝘁𝗿𝗲 𝗧𝗲𝗻𝗮𝗻𝘁𝘀 𝗲𝘀𝘁á 𝗰𝗵𝗲𝗴𝗮𝗻𝗱𝗼 𝗮𝗼 𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗘𝗻𝘁𝗿𝗮! www.linkedin.com/posts/mauric...

#MicrosoftEntra #EntraID #MicrosoftIdentity #MultiTenant #Sincronização #Segurança #Governança #TI #TransformaçãoDigital #Produtividade #CrossTenantSecurityGroupSynchronization

0 0 0 0

Robotron Technology Channel

@technologie.robotron.services

3 months ago

Parallel dazu zieht @dbamarco.bsky.social ins Battle: Multitenant Database oder doch lieber nicht?
Ab 10 Uhr könnt ihr euch auf ein humorvolles, aber fachlich fundiertes Duell freuen: Ist Multitenant die Zukunft oder lieber nicht anfassen, was läuft?
#DOAG2025 #Multitenant

3 1 0 0

Pure Tech

@puretech.news

4 months ago

Building at Production Speed: How Multi-Tenant Systems are Shaping Software Delivery All the technology news you can handle in a single feed

Building at Production Speed: How Multi-Tenant Systems are Shaping Software Delivery #Technology #SoftwareEngineering #Other #SoftwareDelivery #CloudComputing #MultiTenant

1 0 0 0

Ortus Solutions

@ortussolutions.bsky.social

5 months ago

🎯 ColdBox Free Tip #6 – Using Routing with Wildcard Domains
Deploy domain-specific routing in ColdBox using withDomain() — ideal for multi-tenant apps and subdomain logic.

🔗 Check it out: www.ortussolutions.com/blog/coldbox...

#ColdBox #Routing #Wildcards #MultiTenant #CFML #WebDevTips

0 0 0 0

Sulu CMS

@sulu.io

6 months ago

Implement Multi Tenant Architecture in Symfony Multi-tenancy is a crucial architectural pattern for SaaS applications where a single application...

Building SaaS applications? Check out Thibault Beaumont’s comprehensive guide to implementing multi-tenant architecture in Symfony with separate databases per tenant.

dev.to/tbeaumont79/...
#symfony #multitenant #saas

2 0 0 0

The Complete Guide to Zitadel | Course In this course, we will explore the complete guide to Zitadel, a modern identity and access management solution. We will cover everything from the basics of setting up Zitadel to advanced features…

6 months ago

#Multitenant & Data Guard – was kann da schon schiefgehen? Markus Flechtner zeigt DBAs in seiner Session auf der #DOAG2025, wie sie mit Komplexitäten umgehen können und bietet praktische Lösungen und Ratschläge, um diese Technologien effektiv zu nutzen. ➡️ scomp.ly/pqaQZg3

1 1 0 0

Zitadel 🦒

@zitadel.com

8 months ago

👨‍🎓 👩‍🎓 🧑‍🎓 Become an expert at #Zitadel, the #OpenSource #identity platform built for #developers who are tired of legacy #IAM complexity, with @rawkode.dev:
✅ #Multitenant architecture
✅ #Passwordless auth
✅ API-first design
Perfect for #CloudNative engineers!

2 2 0 0

Forem

@forem.com.web.brid.gy

10 months ago

Replacing Prisma Accelerate with Redis and Twemproxy ## Self-Hosting Your Way to Cost Savings: Replacing Prisma Accelerate with Redis and Twemproxy By replacing Prisma Accelerate ($60/month) with a self-hosted Redis caching solution using Twemproxy, we maintained query performance while essentially reducing our database caching costs to zero. The solution works reliably in serverless environments and integrates seamlessly with our multi-tenant architecture. ## The Challenge: Rising Costs with Managed Services Serverless applications need efficient database strategies for good performance, but managed services can get expensive as you scale. When our Prisma Accelerate bill hit nearly $60 last month—approaching the cost of our entire EC2 instance—we knew we needed an alternative. Prisma Accelerate provides excellent connection pooling and caching for serverless environments, but the pricing became a concern as our application grew. ## Our Journey to a Solution ### Research and Discovery Finding a reliable alternative wasn't straightforward. This topic isn't widely covered in existing resources, so I spent considerable time researching different approaches: * Explored various Prisma caching extensions from the community * Tested multiple Redis client libraries and their serverless compatibility * Evaluated different proxy solutions including HAProxy, Envoy, and Twemproxy * Experimented with custom connection management implementations Many solutions worked well in traditional server environments but failed in serverless contexts due to connection management issues. After extensive testing, I discovered that combining the official Redis client, a custom Keyv adapter, and Twemproxy for connection pooling created a reliable solution for our needs. ### Building Our Own Twemproxy Docker Image We couldn't find an official Docker image for Twemproxy that met our needs, so we decided to build our own: 1. **Cloned the Repository** : First, we cloned the Twitter (now X) Twemproxy repository from GitHub: git clone https://github.com/twitter/twemproxy.git 1. **Built the Image** : We built and tagged our custom Docker image: docker build -t twemproxy . This allowed us to have full control over the Twemproxy build and configuration. ### The Winning Architecture We designed a containerized infrastructure leveraging our existing EC2 instance: * **PostgreSQL** : Our primary database * **PgBouncer** : For PostgreSQL connection pooling * **Redis** : For caching query results * **Twemproxy (nutcracker)** : A fast and lightweight proxy for Redis Here's our Docker Compose setup: version: "3" services: postgres: image: postgres:latest environment: POSTGRES_PASSWORD: ${POSTGRES_PASSWORD} volumes: - postgres-data:/var/lib/postgresql/data ports: - "5432:5432" pgbouncer: image: bitnami/pgbouncer:latest environment: DATABASE_URL: postgres://postgres:${POSTGRES_PASSWORD}@postgres:5432/mydb MAX_CLIENT_CONN: 1000 DEFAULT_POOL_SIZE: 20 ports: - "6432:6432" depends_on: - postgres redis: image: redis/redis-stack:latest command: redis-server --requirepass ${REDIS_PASSWORD} ports: - "6379:6379" volumes: - redis-data:/data twemproxy: build: ./twemproxy volumes: - ./twemproxy/nutcracker.yml:/etc/nutcracker.yml ports: - "22121:22121" depends_on: - redis volumes: postgres-data: redis-data: ## Implementation Details ### Configuring Twemproxy for Redis Twemproxy provides connection pooling and can distribute requests across multiple Redis instances if needed. Our configuration: alpha: listen: 0.0.0.0:22121 hash: fnv1a_64 distribution: ketama auto_eject_hosts: true redis: true redis_auth: "your_redis_password" server_retry_timeout: 30000 server_failure_limit: 1 servers: - 172.17.0.1:6379:1 # Docker host bridge IP ### Custom Redis Store Adapter The heart of our solution is a custom Redis adapter that implements the KeyvStoreAdapter interface and handles connection lifecycle properly in serverless environments: // redis.ts import cacheExtension from "@paulwer/prisma-extension-cache-manager"; import { Keyv } from "keyv"; import { createCache } from "cache-manager"; import { createClient, type RedisClientType } from "redis"; class RedisStore { // Implementation details... constructor(options: { url?: string; namespace?: string; client?: RedisClientType; }) { // Setup Redis client with proper reconnection strategy this.client = createClient({ url: options.url, socket: { reconnectStrategy: (retries) => { // Implement exponential backoff const delay = Math.min(retries * 50, 1000); return delay; }, connectTimeout: 5000, }, }); // Connect immediately and handle errors // ... } // KeyvStoreAdapter methods... } export function createPrismaRedis(namespace: string | undefined) { const redisStore = new RedisStore({ url: process.env.REDIS_URL, namespace: `prisma-cache-${namespace}`, }); const keyv = new Keyv({ store: redisStore, namespace: `prisma-cache-${namespace}`, }); const cache = createCache({ stores: [keyv], }); return cacheExtension({ cache, defaultTTL: staleMins(1), useAutoUncache: true, }); } ### Integrating with Prisma We extended our Prisma client to use the Redis cache: // prisma.ts const rawPrisma = globalForPrisma.prisma ?? prismaClientSingleton(); // Global Prisma client with caching export const prisma = rawPrisma.$extends(createPrismaRedis(`global`)); // Merchant-specific client with tenant isolation and caching export const merchantPrisma = (merchantId: number) => rawPrisma .$extends(forMerchant(merchantId)) .$extends(createPrismaRedis(`merchant-${merchantId}`)); ## Multi-Tenant Superpowers One major advantage of our solution is how well it integrates with our multi-tenant architecture: 1. **Isolated Cache Namespaces** : Each tenant gets their own cache namespace, preventing data leakage and cache collisions 2. **Layered Extensions** : We apply tenant-specific filters first, then add caching on top, creating clean separation of concerns 3. **Configurable TTL Per Entity** : Different data types can have different caching strategies The result is a system where: * Each merchant's data remains isolated * Cache invalidation for one tenant doesn't affect others * We can apply tenant-specific business logic before caching * The system scales well as we add more tenants ## Challenges and Solutions ### Socket Connection Issues **Challenge** : Initial attempts with `keyv/redis` adapter resulted in "socket closed unexpectedly" errors in serverless environments. **Solution** : Implemented a custom Redis adapter using the official Redis client from redis.io, which handles disconnections more gracefully with proper reconnection strategies. ### Redis Command Compatibility **Challenge** : Twemproxy only supports a subset of Redis commands, causing issues with client libraries that use unsupported commands like `INFO`. **Solution** : Configured our Redis client to disable features that use unsupported commands: * Setting `enableReadyCheck: false` * Setting `connectionName: null` ## Results: Performance and Cost Savings After migrating from Prisma Accelerate to our self-hosted solution, we observed: * **Performance** : Query response times remained consistent with Prisma Accelerate * **Cache Efficiency** : Cache hit rates improved slightly (5-10%) * **Stability** : Overall application performance remained stable * **Cost Savings** : Monthly costs dropped from $60 to essentially $0 (using our existing EC2 instance) ## Key Takeaways 1. **Connection Management Matters** : Proper handling of connection lifecycles is crucial in serverless environments 2. **Client Selection is Critical** : The Redis client library you choose makes a significant difference in reliability 3. **Cost vs. Complexity Trade-off** : While managed services are convenient, the cost savings of self-hosting can be substantial if you already have infrastructure 4. **Namespace Isolation is Powerful** : Using proper namespace prefixes for different parts of your application prevents cache collisions and improves security ## When to Consider This Approach This approach works well if: * You already have infrastructure you can leverage * You have the technical expertise to maintain it * The cost of managed services is becoming significant * You need custom caching behavior that managed services don't provide ## Resources * Twemproxy (nutcracker) GitHub Repository * Prisma Extension Cache Manager * Redis Client for Node.js * Keyv - Simple key-value storage with support for multiple backends

0 0 0 0

Zitadel goes beyond basic authentication into threat intelligence & analysis of authentication data Florian Forster, CEO & Co-Founder, Zitadel, joins us in this episode to discuss the challenges of authentication in cloud-native and Kubernetes environments, such as managing token expiration,…

11 months ago

"Zahlen, bitte: Wie kann man die Ressourcennutzung von PDBs ermitteln und abrechnen" heißt eine Session von Markus Flechtner @markusdba.bsky.social auf der #DOAGDB25, die wertvolle Einblicke für Administratoren und Architekten bietet, die #Multitenant einsetzen. ➡️ scomp.ly/v60LDmK

2 2 0 0

Zitadel 🦒

@zitadel.com

11 months ago

@fforootd.bsky.social recently spoke to Twain Taylor about how #Zitadel is revolutionizing #authentication — from developer-first approach to threat intelligence — with an #opensource, #multitenant #IAM platform: buff.ly/4hKkCru

1 0 0 0

VincentH.NET

@vincenth.net

11 months ago

GitHub - VincentH-Net/Orleans.Multitenant: Secure, flexible tenant separation for Microsoft Orleans Secure, flexible tenant separation for Microsoft Orleans - VincentH-Net/Orleans.Multitenant

🎉 Orleans.Multitenant 3.0 is out!

✅ Updated to Microsoft Orleans 9.1
✅ Includes how to use with #dotnet #aspire

NJoy
⬇️
github.com/VincentH-Net...

#multitenant #cloudnative #csharp

4 2 1 0

Sascha Stumpler 💻

@sastu-insights.com

11 months ago

New MiToken Graph PowerShell module for multi-tenant apps Connect to multi-tenant apps using a managed identity using Microsoft Graph PowerShell with the MiToken PowerShell module. The post New MiToken Graph PowerShell module for multi-tenant apps appeared first on Our Cloud Network.

New MiToken Graph PowerShell module for multi-tenant apps via PlanetPowerShell #MicrosoftGraph #PowerShell #MultiTenant #CloudComputing

1 0 0 0

VincentH.NET

@vincenth.net

1 year ago

GitHub - Applicita/Orleans.Multitenant: Secure, flexible tenant separation for Microsoft Orleans Secure, flexible tenant separation for Microsoft Orleans - Applicita/Orleans.Multitenant

Fixed example for Microsoft #orleans with #dotnet #aspire and #multitenant #azure blob storage grain state; it uses a new approach that can be used for other grain state providers as well:
👇
github.com/Applicita/Or...

🎁NJoy!

8 0 1 0

VincentH.NET

@vincenth.net

1 year ago

GitHub - Applicita/Orleans.Multitenant: Secure, flexible tenant separation for Microsoft Orleans Secure, flexible tenant separation for Microsoft Orleans - Applicita/Orleans.Multitenant

Want to use #dotnet #aspire with Microsoft Orleans and #multitenant?
👇
How to use Aspire with Orleans.Multitenant:
github.com/Applicita/Or...

Thanks to @reubenbond for pointing me in the right direction!

Also, release 2.2.12 is out with fixes
🎁NJoy!
@msftorleans #multitenant #cloudnative #csharp

3 0 0 0

Sander Rozemuller

@sander.rozemuller.com

1 year ago

Back from London 🇬🇧. Busy week ahead, working an #IntuneAssistant. Some nice features are coming. #multitenant , #policyrestore

3 0 1 0

Multi-tenant organization capabilities now available in Microsoft 365 Discover the new multi-tenant organization capabilities in Microsoft 365, including People Search, Teams, Viva Engage, and Microsoft Defender XDR. Learn how these features can enhance collaboration, c...

1 year ago

#DOAG2024 🌐 | ...featuring #Graphdatenbank #SQL #PatternMatching #Hochverfügbarkeit #Multitenant #Oracle23ai #Autoupgrade #InMemoryDB #SegmentCaching #ObjectCaching #CloudNative #KI #MySQL #MariaDB u.v.a.m. 🤩 Auf der großen Anwenderkonferenz, Nürnberg ➡️...

1 0 1 0

Robert Eriksson 🇪🇺

@roberik.bsky.social

1 year ago

Multi-tenant organization capabilities now available in Microsoft 365

🔗 techcommunity.microsoft.com/t5/microsoft...

#Microsoft #Microsoft365 #Tenant #MultiTenant #MicrosoftTeams #VivaEngage #MicrosoftDefenderXDR #MicrosoftEntra #MicrosoftEntraID #MicrosoftDefender

0 0 0 0

4 years ago

Auch im Zeitalter autonomer DBs wird das #Tuning von DBs und SQL-Abfragen nicht verschwinden. @BleileClemens widmet sich dem Thema Tuning in einer Multitenant-Umgebung in #redstack 02/2021 ab S. 29. http://ow.ly/tT8z50Ew8d4 #multitenant #Administrator #AutonomousDB #SQL

0 0 0 0