3 ms·
Multiple sourcing is the key. All of the above products can be bought from multiple places, this API could be "bought" from a single vendor. Any usage kf SaaS
by blub 8y ago
Multiple sourcing is the key. All of the above products can be bought from multiple places, this API could be "bought" from a single vendor.
Any usage kf SaaS would require a solid contract in place and a plan B (and C, and D, etc) to reach even a fraction the reliability of e.g electricity or food.
- viraptor 8y agoManaging risk comes into play here. Would you spend time integrating 2 services, negotiating 2 contacts, supporting 2 providers who may change features and approaches over time, splitting a fraction of traffic to make sure both still work, limiting yourself to common feature set... Or would that cost you more to implement them a few days of (potential) complete downtime. Choosing the potential downtime is not a failure, if you considered your options.
- sverhagen 8y agoYou have to admit that the Smyte's customer list that's floated around, here, isn't all just some startups that can't afford to research their backups. And maybe they did, actually. Did anyone even hear if Zendesk was even affected by this happening?