For compute: 1. In the beginning (new startup), you don't know what usage looks like. It may not even be used at all at night / during the day. If you're not f

For compute: 1. In the beginning (new startup), you don't know what usage looks like. It may not even be used at all at night / during the day. If you're not full-in on managed services, you're burning money on stuff you're not using. 2. Eventually you start to see consistent use. Run back-of-the-envelope numbers on using something less managed, i.e. Lambda -> Fargate -> EC2. If it makes financial sense to switch, do it. If not, stay where you are. 3. Continue to optimize over time in the direction of bare-metal as your cloud spend hits seven figures and higher. For data: 1. If you have a small amount of data, then managed services are a trap, as services make implicit dependencies on the managed service. Stick to open core. If the amount of data is small, then it won't be too expensive to export it off the environment where it is to a new environment where it will be cheaper. 2. If you have a large amount of data, then your data is probably locked into whichever environment / provider is hosting it anyway, due to egress issues (either via network or via logistics shipping drives). You might as well use a managed service and reduce talent dependencies, as described in the article.