Fighting vendor lock-in and designing testable serverless apps

Re:Fighting vendor lock-in and designing testable serverless... by kensey on Tuesday April 23, 2019 @01:39PM (#19730956)

You can easily grow so large that you hit a limit of what a given cloud provider will allow (e.g. API calls or IOPS) at a price that fits into your budget for a task, even if you're not actually especially large. (AWS will give you all the IOPS you can ever use... as long as you have the money to pay.) In that case, being able to pivot to another cloud provider quickly can save your burn rate.

(Flashback to my ITIL instructor in 2008 talking about Service Catalogs and how they are meant to include even discontinued products. "Will Microsoft support Windows 3.1 for you today? YES! Bring money.")

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by scarface74 on Tuesday April 23, 2019 @01:59PM (#19731130)

And you think you can host on prem and support your use cases without any budgetary constraints?

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by regularfry on Tuesday April 23, 2019 @03:18PM (#19731910)

Is "on prem" the same as "another cloud provider"? Or is it irrelevant to the discussion?

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by scarface74 on Tuesday April 23, 2019 @03:25PM (#19731978)

If you need resources, either you’re going to have to pay a cloud provider or run them in your own data center or at a colo.

[ Parent | on HN ]