fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.6K
active users

#multitenancy

0 posts0 participants0 posts today

☠️ Oh joy, yet another tale of how #SQLite3 becomes a sardine can when you try to cram in #multitenancy with Rails! 🐟 Apparently, the author's groundbreaking revelation is that ignoring #multithreading makes your app collapse faster than my interest in reading this. 🚀
blog.julik.nl/2025/04/a-can-of #Rails #Issues #SardineCan #HackerNews #ngated

Julik Tarkhanov · A Can of Shardines: SQLite Multitenancy With RailsThere is a pattern I am very fond of - “one database per tenant” in web applications with multiple, isolated users. Recently, I needed to fix an application I had for a long time where this database-per-tenant multitenancy utterly broke down, because I was doing connection management wrong. Which begat the question: how do you even approach doing it right? And it turns out I was not alone in this. The most popular gem for multitenancy - Apartment - which I have even used in my failed startup back in the day - has the issue too. The culprit of does not handle multithreading very well is actually deeper. Way deeper. Doing runtime-defined multiple databases with Rails has only recently become less haphazard, and there are no tools either via gems or built-in that facilitate these flows. It has also accrued a ton of complexity, and also changes with every major Rails revision. TL;DR If you need to do database-per-tenant multitenancy with Rails or ActiveRecord right now - grab the middleware from this gist and move on. If you are curious about the genesis of this solution, strap in - we are going on a tour of a sizeable problem, and of an API of stature - the ActiveRecord connection management. Read on and join me on the ride! Many thanks to Kir Shatrov and Stephen Margheim for their help in this.

❇️ Unlocking #AI Potential with #Kubernetes & Key Benefits 🌐

Kubernetes is revolutionizing AI deployment with its scalable and efficient container orchestration capabilities.

Here are the key perks:
🔹Scalability: Automatically scales AI workloads to handle surges in demand, ensuring seamless performance.
🔹Efficient Resource Management: Optimizes CPU, GPU, and memory allocation based on workload needs, reducing costs.
🔹Multi-Tenancy: Allows multiple teams to share resources without interference, enhancing collaboration.
🔹High Availability: Ensures AI applications remain operational even during hardware failures, thanks to self-healing capabilities.
🔹Seamless Deployment: Enables consistent deployment across different environments, from on-premises to cloud.

klizos.com/kubernetes-ai-deplo

#Kubernetes #AI #MachineLearning #Scalability #Efficiency #MultiTenancy #HighAvailability #CloudNative #DevOps #CI/CD #ContainerOrchestration #ITInfrastructure #Innovation #TechTrends #CloudApplications #DataProcessing

Solve the multi-tenancy problem in Kubernetes and reduce costs at the same time? 🤔 Virtual clusters – aka vClusters – have their own API server and are therefore more powerful and better isolated than namespaces. 🚀🏝️ But that's not all: they are also much cheaper than real Kubernetes clusters. 💰 You can find all further details about our vCluster offer here nine.ch/products/vcluster/ on our website. 🔗 #vcluster #kubernetes #multitenancy #namespaces #nine

We're having a little think about multi-tenancy at Octopus. It was a hot topic in the early 2000s due to the rise of SaaS... but then we just took it for granted.

I think it's worth another look as the old model is based on things that have changed.

Here's a 12-minute video about a new approach to #MultiTenancy to start the conversation...

youtube.com/watch?v=GB6IYvCf_C