Comment by JackSlateur

Comment by JackSlateur 3 days ago

Haa, yes, the scary "vendor lock-in" !

I challenge you : give me a single product that cannot be moved away, given some (cost or time).

At the same time, I again challenge you : give me a single product that you can move between providers with no cost nor time.

To that last one, you can actually find stuff. For instance, you could setup your nginx in instances, without any kind of interactions with the hosting provider. In which case, you limit yourself with what everybody can do, leaving all opportunities to only use the base minimal.

But wait .. are you not locked-in with nginx (or to use a better example: with redis) ?

Vendor lock-in is a scam to increase your bills. Because, in itself, everything is vendor locking. And it does not matter. Think your architecture, design your code, and act when necessary.

candiddevmike 3 days ago

I don't think you've ever been through the pain of moving a big, fully integrated, multiple ETL pipeline data warehouse built on something like Redshift. Vendor lock in is more about inertia and less about there not being an alternative. Some things are just really, really difficult to move and ridiculously impactful to change.

Reply View 0 replies

freedomben 3 days ago

You seem to be trying to reduce the vendor-lockin issue to a binary "locked" or "not locked," but Idon't think that's a productive or realistic way to think about it. It's really more of a spectrum, and I prefer to think about it as "options" rather than "are we locked." You definitely have a lot more options if you go with Nginx and the project turns evil than you would if you went with some proprietary offering.

Reply View 0 replies

unethical_ban 3 days ago

You take the term "lock-in" far too seriously.

Yes, one can migrate their entire CI/CD ecosystem, countless IAM policies across multiple AWS accounts in an organization, their lambdas, databases and S3 buckets over to Azure given enough time and money.

The thing is that most everything in the cloud is billed on subscription, and many core components of networked services need not be (except support). Open file server, self-hosted IAM and standards-based execution stacks. Don't like hosting your nginx on Vendor-A? Move it to Vendor-B.

Yes, the tradeoffs are costs. No, vendor "lock-in" is not the only component one should measure when deciding an architecture. Yes, "lock-in" can occur with on-prem software, and hardware, as well.

Yes, it's real and worthy of concern when a vendor knows they can squeeze you because you have no other choice and the level of effort to migrate is too high.

Reply View 0 replies