Samsung Migrates 1.1 Billion Users across Three Continents from Oracle to Amazon Aurora

Samsung Migrates 1.1 Billion Users across Three Continents from Oracle to Amazon Aurora

  • June 24, 2020
Table of Contents

Samsung Migrates 1.1 Billion Users across Three Continents from Oracle to Amazon Aurora

Samsung completed the EU migration by April 2019, the China migration by October 2019, and the US migration by March 2020, all with minimal downtime. “We had some downtime but not much,” says Jung. “The important thing is that we detected problems quickly and minimized the user impact.

After the migration, Samsung is fully prepared for future growth. For example, Aurora now allows Samsung to seamlessly scale up to 15 Aurora Replicas—independent endpoints in an Aurora database cluster used for scaling read operations and increasing availability—across the availability zones in each region. With the scalability of Aurora, Samsung can serve more users more quickly than before: now 90 percent of latency is less than 60 ms.

The automation of the cloud solution also allows Samsung to deliver more features to users faster. According to Byungyul Ko, Samsung’s database administrator, the company saves 44 percent on monthly operational costs with Aurora PosgreSQL compared to Oracle, on top of the additional Oracle expenses of a pricey IDC license fee and another 22 percent in maintenance fees. With Aurora, Samsung pays as it goes and only pays for what it uses, with no upfront fee or restrictive licenses.

Source: amazon.com

Tags :
Share :
comments powered by Disqus

Related Posts

Cloud-Powered, Next-Generation Banking

Cloud-Powered, Next-Generation Banking

Traditional banks make extensive use of labor-intensive, human-centric control structures such as Production Support groups, Security Response teams, and Contingency Planning organizations. These control structures were deemed necessary in order to segment responsibilities and to maintain a security posture that is risk averse. Unfortunately, this traditional model tends to keep the subject matter experts in these organizations at a distance from the development teams, reducing efficiency and getting in the way of innovation.

Read More