Re:Running Databases on Kubernetes
by barrkel on Thursday March 02, 2023 @06:31PM
(#35003583)
What if you have finance customers who don't like commingled data, and you want to sell them a service and tell them with a straight face that their tenanted database isn't one bad query from serving up their data to someone else?
[ Parent
| on HN ]
Re:Running Databases on Kubernetes
by yesbabyyes on Thursday March 02, 2023 @06:34PM
(#35003608)
You can still have separate ACLs, databases, tables and even row level access control even if you share database servers.
You can also have dedicated database servers per customer on bare metal or VMs. It's not always more work than asking your database team to learn Kubernetes...
Re:Running Databases on Kubernetes
by seanhunter on Friday March 03, 2023 @05:50AM
(#35008002)
Speaking as someone who has sold Saas into banks numerous times, "no shared tenancy" is very frequently an absolute and non-negotiable requirement.
Re:Running Databases on Kubernetes
by yesbabyyes on Friday March 03, 2023 @06:19AM
(#35008166)
Fair enough; as 'twblalock says, it doesn't have to be more arduous to set up database servers per seat outside of k8s.
I simply wanted to highlight that there are many ways to skin a cat, and "no shared tenancy" is not in itself a valid argument for hosting your DBs in k8s, even though there may be other good reasons.