Earlier quoted context omitted.
There's little risk of depending on external services if you use multiple that provide the same type of service hidden behind an abstraction layer and can remove one of the vendors from the mix with the press of a key.
That mitigates the risk of depending on services, but it introduces a huge new risk by committing development time to a feature that provides no value to the user and potentially, if the providers last, no value to the business either. Any startup founder who follows this strategy is concentrating on the wrong thing. Pick the provider who's most likely to last and build against their service. That way you are more li…
You're conflating "using an external product" with "using an external service". The third option is self-hosting a third-party product, which gives you the best of both worlds (reduced development cost and time, reduced risk due to continued reliance on third party).
