3 ms·
When you go "full serverless", you still need a place to store data, backups, etc. And then with the high cost of bandwith (...) you may as well use the same se
by chronid 10y ago
When you go "full serverless", you still need a place to store data, backups, etc. And then with the high cost of bandwith (...) you may as well use the same service provider you use for your "services". Be it AWS or GCloud or Azure.
If you spin up servers to manage your database+storage needs, then you are no longer serverless, you are in a pretty nice hybrid - lowering somewhat your money costs maybe, but I'd still argue that the impact on ops of the "application servers" is negligible compared to what is required by everything else in the stack.
- WolfOliver 10y agoThere is a slightly better name for "serverless architecture", its called "function as a service". But in my opinion "process on demand" would describe this concept even better.