Source: dzone.com
Heroku - My New HomeCategory: Deployment, Business, Database, container, gitlab
In the "Moving Away From AWS and Onto Heroku" article, I provided an introduction of the application I wanted to migrate from Amazon's popular AWS solution to Heroku.
The third article in the series ("Using Heroku for Static Web Content") provided a manner in which static web files could also be serviced by Heroku.
From an application and design perspective, there was literally no change to the application, now running 100% in Heroku: The image above is an identical copy of the image which was in part one of this series.
While the application was very easy to port over to Heroku, there were changes in the manner by which the application is updated and deployed now.
While the buildpack is experimental and not a product by the Heroku team, I feel like the stability is certainly at a level by which I would trust for my application.
The third article in the series ("Using Heroku for Static Web Content") provided a manner in which static web files could also be serviced by Heroku.
From an application and design perspective, there was literally no change to the application, now running 100% in Heroku: The image above is an identical copy of the image which was in part one of this series.
While the application was very easy to port over to Heroku, there were changes in the manner by which the application is updated and deployed now.
While the buildpack is experimental and not a product by the Heroku team, I feel like the stability is certainly at a level by which I would trust for my application.
Related Articles
Community Partners
DevOps Careers