Re:Lyft Files S-1
by spookthesunset on Friday March 01, 2019 @05:49PM
(#19286089)
> The trouble is when people build around Amazon, they get locked into a lot of those services.
The trouble when people build things that have nothing to do with their core value propositions, they get locked into those services too. It is very easy for companies to get locked into their own homebrew garbage frameworks, clustering solutions, reporting & data analysis apps, or whatever else people hacked up because "omg vendor lockin!!".
Seriously, I hear the same argument with frameworks too. At the end of the day it isn’t a choice between framework A and no framework, it’s going to be a framework A and your custom baked framework, and do you really have the time to spend reinventing the wheel?
Re:Lyft Files S-1
by CondensedBrain on Friday March 01, 2019 @02:48PM
(#19284588)
Netflix and its (ongoing?) transition from AWS to its own systems might provide some guidance if they ever decide to do the same.
What transition are you talking about?
Re:Lyft Files S-1
by CondensedBrain on Saturday March 02, 2019 @08:07AM
(#19289074)
The one I misremembered and that apparently never happened.
You have to rewrite application to use something else that's open source and self-hostable.
For new startups, I honestly recommend using DigitalOcean or Vultur. You don't get all the AWS components, but you can build around flexibility. If you have to move, you can take all your Terraform and Anisble scripts, and port them to a new provider (and yes, you do have to rewrite your Terraform config. Every provider is insanely different and the magic of multi-cloud is a myth, but it's still easier than trying to move off of AWS specific services).
I remember back in the day, Stackoverflow ran everything off of a single, very expensive, dedicated server. I've worked at other shops where we've migrated stuff from AWS to self hosted solutions to reduce our $200k/month AWS bill.