|
|
|
|
|
by donavanm
519 days ago
|
|
It definitely scales of complexity/surface area, and Id say that straight number is a lower bounds fixed cost that you might see from an unsuccessful “small” service. In larger orgs its better a percentage, because its relative to overall investment/growth. My personal goal would be 20% ktlo, usually much closer to 40% in practice. All based on my personal experience doing the cloud thing across 2 companies for 15 years or so. And I will give credit to AMZN/AWS, of old at least, that the above would be common knowledge with an expectation of much more org specific details for anyone sr manager/PE through VP whod be involved in roadmaps, HC allocation, etc. |
|