3 ms·

I agree with the idea, but I also think there are limits. Let's say you build some kind of product based on some Azure/AWS product. The negative reading of it

I agree with the idea, but I also think there are limits. Let's say you build some kind of product based on some Azure/AWS product. The negative reading of it is: you spend money on innovation and have to pay Azure/AWS for infrastructure. Your product will constantly have to improve to keep up with the competitors, Azure/AWS keeps getting your money. And if your product becomes stable enough, they will make it part of their offering. Another example would be Apps, with Apple later folding their functionality into the OS and kicking your app off the store. But judging by my own examples, this migth be more of a platform problem.

NomDePlum 7y ago
Surely that very much depends on whether your product fits within the current or near future offering of Azure/AWS. The other side of that coin is that you use a build horizontal integration strategy to replace elements of the products you buy from Azure/AWS if (and only if) it can be done in a way that increase your profit/value. It can work both ways. Moving from buy to build also has elements of de-risking and economies of scale if you do it at the point where there is measurable success/product to market fit. Building something you can buy too early runs the risk of premature optimisation if not done for the right reasons.
- HolaDonPepito 7y ago
  :O