3 ms·

Pretty telling that the top two comments at the moment endorse the two most diametrically opposite approaches possible: single app and single set of tables with

by zzzeek 6y ago

Pretty telling that the top two comments at the moment endorse the two most diametrically opposite approaches possible: single app and single set of tables with row level security, vs totally separate apps + separate dbs entirely. I think it really depends on the kind of application and the kind of user / customer you're dealing with. I'd probably lean towards "single" database with horizontal sharding .

stingraycharles 6y ago
Yup, we use “single tenant” as a major upsell to enterprises, and just run a kubernetes cluster for each of these, with their own maintenance / release cycles. But we can only do that because they pay a lot of money for this stuff. Our “shared, multi-tenant” environment is an order of magnitude cheaper.
- HatchedLake721 6y ago
  Out of personal interest as someone who’ll be offering pricier “single tenant” or “we’ll deploy to your AWS account”, how do you price this?
  - polack 6y ago
    We charge about 10x for enterprise customers. The only difference between what they get and what a normal customer get is that we deploy the enterprise customers on their own servers/network. Considering how long end exhausting the sales process are with enterprise customers I think the price is fair, even though the extra cost to operate that kind of customer is negligible.
    - user5994461 6y ago
      I'd add that the minimum bill is $10000 for anything enterprise. That's a bare minimum to handle all the time and extra work they will incur (months of sales process, dedicated AWS instances, heavy support burden, single sign on integrations, etc...). As soon as you hear any of these, it's the hint you're dealing with enterprise and you have to up the price tenfold.
- mvanbaak 6y ago
  Does this scale?
  - stingraycharles 6y ago
    Good question. It does, in the way that we use the same software everywhere, the same docker containers and everything. On the other hand, it takes a lot more effort to manage releases. I guess it scales in the same way Microsoft’s enterprise business scales; hard labor on top of a scalable platform.

by zzzeek 6y ago

stingraycharles 6y ago

Yup, we use “single tenant” as a major upsell to enterprises, and just run a kubernetes cluster for each of these, with their own maintenance / release cycles. But we can only do that because they pay a lot of money for this stuff. Our “shared, multi-tenant” environment is an order of magnitude cheaper.

HatchedLake721 6y ago
Out of personal interest as someone who’ll be offering pricier “single tenant” or “we’ll deploy to your AWS account”, how do you price this?
- polack 6y ago
  We charge about 10x for enterprise customers. The only difference between what they get and what a normal customer get is that we deploy the enterprise customers on their own servers/network. Considering how long end exhausting the sales process are with enterprise customers I think the price is fair, even though the extra cost to operate that kind of customer is negligible.
  - user5994461 6y ago
    I'd add that the minimum bill is $10000 for anything enterprise. That's a bare minimum to handle all the time and extra work they will incur (months of sales process, dedicated AWS instances, heavy support burden, single sign on integrations, etc...). As soon as you hear any of these, it's the hint you're dealing with enterprise and you have to up the price tenfold.
mvanbaak 6y ago
Does this scale?
- stingraycharles 6y ago
  Good question. It does, in the way that we use the same software everywhere, the same docker containers and everything. On the other hand, it takes a lot more effort to manage releases. I guess it scales in the same way Microsoft’s enterprise business scales; hard labor on top of a scalable platform.