


“I don’t think they can do it They’ve had 10 years to get off Oracle and they’re still on Oracle. In 2018, Ellison commented, “there is no way that… any normal person would move from an Oracle Database to an Amazon Database.”Įllison’s philosophy on what classes as normality aside, he also expressed doubt about Amazon’s capabilities.

The lead up to Oracle and Amazon going their separate ways has involved some entertaining challenges from Oracle’s CTO Larry Ellison. In short, Amazon’s ERP environment couldn’t keep up with its requirements, and this ongoing issue was keeping Amazon from dedicating its time to more high-value work. Amazon Web Services CTO Werner Vogels wrote off the “90’s technology” behind most relational databases. Their own database administrators were mostly focused on just keeping their systems running, while their data – and Oracle’s prices – continued to rise.Īmazon was also dealing with complex and inefficient hardware provisioning, licence management, and many other issues that are now best handled by modern, managed database services. Through doing so, the team at Amazon realised just how much time they were wasting on managing and scaling their thousands of legacy Oracle Databases. Put simply, Amazon migrated its systems probably for the same reasons you might consider moving.Īmazon evaluated its internal systems to ensure they were as efficient, secure and performing as well as they could be. All had to be moved across and integrated into its own AWS database services. It required a move of 75 petabytes of internal data stored in nearly 7,500 Oracle Databases. On 1 November, it turned off its Oracle data warehouse, and in a huge act of on-premise hosting, migrated their enterprise from Oracle to its own Amazon Web Services (AWS). Amazon leaves Oracle – cause to celebrate in November 2019.
