![]() ![]() We were pushing the limits of what was a leading commercial database at the time and were unable to sustain the availability, scalability and performance needs that our growing Amazon business demanded. We had an advanced team of database administrators and access to top experts within Oracle. ![]() It all started in 2004 when Amazon was running Oracle’s enterprise edition with clustering and replication. As Vogels described, Amazon was simply trying to take care of its increasingly demanding database needs, as Oracle wasn’t keeping pace. Scratching the itchĪmazon didn’t set out to topple Oracle. ![]() But by scratching an internal itch for greater scale, Amazon set up the start of a database war that threatens Oracle’s long-term dominance. Dynamo wasn’t the first NoSQL database, nor is the subsequent DynamoDB the biggest challenger to Oracle. In so doing, Amazon arguably began to lay the foundation for a clear and present danger to Oracle’s database reign. As Amazon CTO Werner Vogels outlined, Amazon’s “straining database infrastructure on Oracle led us to evaluate if we could develop a purpose-built database that would support our business needs for the long term.” Dynamo was born, initially as a published paper that launched a series of promising NoSQL databases like Apache Cassandra. Amazon had a need for a non-relational, highly scalable approach to data, and every enterprise is now swimming in NoSQL as a result. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |