4 ms·

Curios - what's the use case for a Serverless DB?

• deleted 7y ago
  [deleted]
• davnicwil 7y ago
  It says it's ideal for unpredictable load or infrequent demand. My reading is that billing is done per minute only while the database is being read / written to (active), but what I'm not sure about is if the storage is completely free whilst it's inactive. If that's the case it would seem like a great solution for BI and analytics type applications where you want to collect data over time (and are able to batch writes) and produce reports relatively infrequently.
  • 013a 7y ago
    The storage is definitely not free, even while inactive.
• danenania 7y ago
  A few I can think of: - Your workloads are both bursty and mission critical. Returning errors while you scale up manually isn’t acceptable. - You’re deploying self-hosted software. A serverless db makes it easier for your customer and your support team—capacity planning and scaling are much easier. - You have a small team and want to minimize how much time you spend on ops.
  • northstar702 7y ago
    Is there any scenario where you wouldn't want to use a serverless db? Makes me wonder why any db shouldn't be serverless in this data and age for the benefits that you mention.