5 ms·

Oh boy what do we tell everyone using AWS?

• rapnie 4y ago
  Rather those offering value-added services on top of AWS. Well, maybe they read HN and they should account for the risks anyway.
• Espressosaurus 4y ago
  The risk is always that they decide the service you're relying on is too niche/is being replaced by something else and you need to adapt. Which is a thing that happens. The big stuff like EC2 isn't likely to go away before Amazon itself goes away, but there are piles of other smaller services that may or may not. It's not Google in terms of getting rid of capabilities, but they sunset APIs and capabilities all the time. For good reason! It's probably not a good idea to be running Python 2.7 today, and there's no reason why they should want to support it. So you're being snide but yes, this is a concern, and the deprecation schedule is solely under Amazon's control. If at some point the cloud goes bust because on-prem is the new hotness (what's old is new again) in 10 or 20 years, you bet your damn bippy AWS will pull the plug when it makes sense for Amazon to do so. And that's a product you pay for. If you're not paying for the product (I don't know if Twitter was offering free access to its APIs) then you're relying on the good will and support of the person/company providing the product/API and at any moment they can change their mind. As we've seen here. If you rely on someone else's platform, you are at their mercy. If you don't believe me, wait another few days for yet another app developer to complain about getting locked out of an app store, or some payments platform locking them out of their account to the tune of hundreds of thousands of dollars.