Heroku bitnami rubystack5/29/2023 ![]() I touched on how one might implement this in my IaaS vs PaaS comparison above. It may be an issue for you, I don't know. Several colleagues have expressed issues with these technologies and the strength of their isolation I am alas not in a position of enough knowledge / experience to really comment, but my current Heroku deployments consider that "good enough". Their article on Dyno Isolation details their isolation technologies (it seems as though multiple dynos are run on individual EC2 instances). When you deploy, you're effectively handing your code straight over to Heroku. With Heroku, you have someone else managing that sort of thing, which is either a blessing or a curse depending on how you look at it! I've seen a lot of internally-maintained production servers that are way behind on security updates, or just generally poorly put together. For others, it's potentially more of a consideration. For you, this sounds like what you want anyway. Now to address your specific points: SpeedĬurrently Heroku only runs on AWS instances in us-east and eu-west. Hopefully that gives you an idea of the comparison between the two. You're using Puppet for your EC2 deployment, right? So now you configure your Capistrano files to spin up/down instances as needed you re-jig your Puppet config so Varnish is aware of web-worker instances and will automatically pool between them. So you're this far, and you want to scale up. With Heroku, the effort required to get to that sort of stage is maybe a few lines of application code and a git push. That's not an insignificant amount of work to set up and maintain. You'll want a deployment system with something like Capistrano, and something doing log aggregation. Varnish), you'll want instances running something like Passenger and nginx to serve your code, you'll want to deploy and configure a clustered database instance of something like PostgreSQL. To get your code running on AWS and looking a bit like a Heroku deployment, you'll want some EC2 instances - you'll want a load balancer / caching layer installed on them (e.g. IaaS can give you more power and flexibility, at the cost of having to build and maintain more yourself. What's the difference? Very approximately, IaaS gives you components you need in order to build things on top of it PaaS gives you an environment where you just push code and some basic configuration and get a running application. AWS offer Infrastructure as a Service ( IaaS) whereas Heroku offer a Platform as a Service ( PaaS). First things first, AWS and Heroku are different things.
0 Comments
Leave a Reply. |