3 ms·
If going Oracle played even a minor part in Amazon's success, then it was a fantastic call, even if now they have a migration task on their hands. Both of thes
by abraae 8y ago
If going Oracle played even a minor part in Amazon's success, then it was a fantastic call, even if now they have a migration task on their hands.
Both of these things can be true:
- we succeeded by betting the farm on a single vendor
- now we need to cut that dependency
- scarface74 8y agoI’m no more saying it was a bad idea at the time than Apple basing iTunes and later the App Store on WebObjects. If I’m consulting a startup that needs to move fast and get off the ground, I’m not going to tell them to worry about “vendor lock-in”. I’m going to tell them to use a cloud provider, use whatever “proprietary lock in” technology they need to to help them move fast and get funding and later if they grow big and they see thier needs change, then maybe suggest an alternative when it makes sense to hire a bunch of internal netops people to babysit servers. But get a developer who knows there way around AWS/Azure and hire a third party company that can do some of the heavy lifting will save a lot money. Yeah I consider myself one of those people. I think I can go toe to toe with most “AWS Architects” that only know netops especially since most of them don’t know development or devops on AWS.