Fighting vendor lock-in and designing testable serverless apps

Re:Fighting vendor lock-in and designing testable serverless... by robrtsql on Tuesday April 23, 2019 @10:16AM (#19728787)

I think it's the other $1975 that is breaking their startup.

Depending on your perspective, that might also be a small amount, but let's not misrepresent the situation.

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by maxxxxx on Tuesday April 23, 2019 @10:22AM (#19728868)

The question is how much you can shave off the 1975 by going to another vendor.

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by acct1771 on Tuesday April 23, 2019 @10:56AM (#19729233)

The question should be how much you can save by not tying an anchor you don't control the weight of around your neck in the first place.

The anchor in the metaphor is using large tech conglomerate without being able to quickly pivot away from them at a moment's notice.

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by spookthesunset on Tuesday April 23, 2019 @04:29PM (#19732507)

> The question should be how much you can save by not tying an anchor you don't control the weight of around your neck in the first place.

How much did it cost to engineer your product to not "tie an anchor"?

My guess is, you didn't "save" anything trying to build out several layers of abstraction to deal with a hypothetical risk of getting screwed by "large tech conglomerates".

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by acct1771 on Wednesday April 24, 2019 @03:43PM (#19741973)

Send me an email, subject "Does your product have technical debt?" in 5 years.

Spoiler: Answer will be "no".

[ Parent | on HN ]