Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Database migration from Heroku to Amazon Web Services

Luong Vo
October 25, 2018

Database migration from Heroku to Amazon Web Services

Luong Vo

October 25, 2018
Tweet

More Decks by Luong Vo

Other Decks in Programming

Transcript

  1. The beginnings Our Company A Web-based all-in-one HR benefits and

    payroll platform. Our need A place to host our web app and store our data. Heroku “A platform as a service that enables developers to build, run, and operate applications entirely in the cloud.”
  2. Challenges Cost Heroku operates on AWS Which makes it more

    expensive than AWS by nature. The same applies for Heroku database offerings. Deployment is not flexible even at higher pricing plan. Customization Lock-in Heroku lets us scale without knowing the infrastructure deeply. Hard to expand to other regions. Hard to integrate with other advanced services. Performance Stable but unpredictable Heroku’s performance is pretty stable, but in case of regressions it doesn’t provide any methods to monitor our database and is unfixable.
  3. Enhanced security 1. Database access is restricted to only the

    servers and people who need it. 2. We can limit database users with various permission levels. 3. Even if somebody did have the connection information, they still couldn’t access the database without being able to get inside the VPC. 4. …. Simply superior to Heroku