18 ms·
According to your definition Heroku is serverless. Serverless widely understood as: 1. not having to deal with instances/dynos/droplets/etc. 2. Pay-per-use,
by nivertech 9y ago
According to your definition Heroku is serverless.
Serverless widely understood as:
1. not having to deal with instances/dynos/droplets/etc.
2. Pay-per-use, no upfront payment for unused capacity
Some calling AWS DynamoDB - serverless, but having to pay for reserved capacity for each table and index, make it a bad fit for the rest of serverless stack like AWS lambda or API Gateway or even S3.
- tpetry 9y agoThe Google redis service will be serverless if the pricing table is not mapped to „subscriptions“ you choose from but instead automatically chooses the pricing layer each hour based on your stored amount (like automated discounts for vms). Thats what i am saying: We still dont know if you have to choose first which pricing layer you want or if google automatically seitches you to the one fitting the amount you store. Both requirements would be fullfilled on automatic selection of pricing layer: 1. You sinply store data, google handles the price/gb-hour depending on your stored amount 2. You only store data and you are only billed the stored amount (in 1GB increments) I just wanted to say we just dont know yet whether its serverless (instance type changed automatically) or you have to choose the instant type first.
- gcbirzan 9y agoYou have to pick the instance type beforehand. Back when I asked about this in the alpha, I was told changing the size of the instance flushes the cache on the basic instance and has some downtime. I can confirm this happens now that resizing is available. For standard, it should be relatively seamless (no flush, minimal downtime), but I'm not gonna test right now. :-)