At the beginning of our program, we chose Amazon Deployment instead of deploying our program on Heroku. Because Heroku has an automatic hibernation when the application is not accessed for a short period of time. As a result, I suggested that we could deploy our code on the AWS server.
However, I spent a lot of time in the this month dealing with AWS deployments. As I learned more about the AWS server, I realized that deploying our application on AWS is much harder than Heroku, and it's not exactly free. We needed to deploy our front-end and back-end separately, which meant we needed two servers. This is where the problem came in, the servers would be on for longer than the free usage of AWS. So we started planning whether to switch from AWS Server to Heroku Server because deploying our application on Heroku is very easy and it's free.
In addition, we found that automating the deployment on AWS is tedious. In contrast, Heroku is very convenient and supports one-click auto-deployment. In fact, we may have made the right choice. When I switched from AWS to Heroku Server, the process went very smoothly.
Actually, I have to admit that deploying the application on AWS Server took me almost two weeks, and the process was a constant learning curve, but there were always obstacles, or maybe it was a learning style. It seems that deploy the application on AWS is very very complicated. I need to create the Ubuntu Server and get the SSL certificate for accessing the application by HTTPS, set up the Auto-Deployment by myself. As a result, we decided to deploy our application on Heroku finally.
