“Lambda and serverless is one of the worst forms of proprietary lock-in” (2017)

Re:“Lambda and serverless is one of the worst forms of propr... by api on Monday February 04, 2019 @06:03PM (#19081567)

There's a middle ground here. You can decide on a case by case basis how much lock-in you are willing to tolerate for a particular aspect of your system. You can also strategically design your system to minimize lock-in while still leveraging provider specific capabilities or "punting" on versatility when you want to.

In other words you can decide to not bother with worrying about lock-in when it costs too much.

This will make your code base easier to port to multi-cloud in the future if you should ever want to.

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by halbritt on Monday February 04, 2019 @07:18PM (#19081979)

Obviously, there's a huge cost associated with the learning curve, but this the part of the reason that Kubernetes is so attractive. It abstracts away the underlying infrastructure, which is nice.

At any kind of scale, though, one is loosely coupled to the cloud provider in any case for things like persistent disk, identity management, etc.

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by scarface74 on Monday February 04, 2019 @06:13PM (#19081635)

Or the old “I use the Repository Pattern to abstract our database so sure we can move our six figure Oracle installation to Postgres”.

And then watch the CTO throw you out of his office.....

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by Aeolun on Monday February 04, 2019 @07:12PM (#19081947)

He didn’t want to hear? Why anyone would build on top of Oracle still eludes me.

Atlassian is bad, but Oracle is on a whole different level.

[ Parent | on HN ]