4 ms·
I would build/buy some kind of service broker that takes queries and passes them to the service.
by sharemywin 9y ago
I would build/buy some kind of service broker that takes queries and passes them to the service.
- sharemywin 9y agomight also have a backup container on competing platforms(AWS/Azure) so you have most of the deployment worked out should things goes south with a provider. Although those types of risks probably aren't worth chasing as early stages.
- sharemywin 9y agoalso, if your chasing a single point of failure then you probably need to diversify if possible. look at the chip maker that just collapsed because apple stop using them. or many businesses that got killed buy walmart's bad contract terms.
- austinjp 9y agoIf I understand correctly, you're suggesting a startup in this position would buy access via a broker who might offer a single API which can be used to access all upstream business-critical APIs..? True... although it feels a little like "kicking the can down the road". Now you have two dependencies: the broker themselves and the upstream API providers. As an investor I'd still ask "What would you do if the broker revokes your API?" -- and now I'd also want to do due-diligence on the broker by asking them all the above questions too. Additionally the broker may be prohibitively expensive. See this recent discussion about teller.io which in part prompted this question: https://news.ycombinator.com/item?id=14605342 https://news.ycombinator.com/item?id=14605342
- sharemywin 9y agopersonally I would build a service broker. it mitigates the technical risk some. Consolidates the code dependencies to the service broker. You will need to build a translation if you switch services.