8 ms·
We're discussing Figma's spend here which is a bit of a cherry pick. At their size the savings for on-prem can be substantial. For the vast majority of companie
by gausswho 1y ago
We're discussing Figma's spend here which is a bit of a cherry pick. At their size the savings for on-prem can be substantial. For the vast majority of companies without such heavy bandwidth needs, the additional cost needs to be measured in terms of additional intenance and staffing.
- vidarh 1y agoSavings can be substantial at much smaller sizes and generally devops maintenance/staffing costs goes down if anything. This is literally my bread and butter, and we make more money off customers who insist on staying on cloud providers, because they consistently need more help.
- gausswho 1y agoI'm curious what size and use case you're serving describing here. Up to a certain point, devops effort and cost is negligible when offloading to the cloud.
- vidarh 1y ago"Negligible" varies greatly from organisation to organisation. People tend to come to my consultancy with needs that'll cost them anything from a few hours a month and up of access to a devops resource. That tends to involve far smaller setups for cloud users than for managed hosting. How large the setup is before that point varies a lot by organisational maturity and what exactly they do, but that can typically reflect hosting costs ranging from a couple of thousand a month and up. But the biggest cost differential is the hosting itself. It's not unusual for a managed setup to cost half or less what the equivalent cloud environment does, for similar levels of resiliency, including the fully loaded cost of devops resources.