Using Heroku For Ruby on Rails

Using Heroku For Ruby on Rails

Heroku is a PaaS platform – supporting a number of web application frameworks including the likes of Ruby on Rails, NodeJS and PHPs Laravel.

The service was designed in 2007 as a way for Rails (and other web application) developers to deploy their applications without having to worry about inner architecture & sever setup.

Its been produced to give people access to single click deploy functionality – allowing them to essentially provision and deploy server instances without the need of having to be concerned about how the infrastructure will work.

This tutorial explores how youre able to use Heroku for Ruby on Rails application development.

The most important thing to understand is that its a closed platform.

In an attempt to be as easy-to-use as possible, the team decided to remove *any* sort of specification from the system. This method that its tied into Amazons EC2 platform, and basically prevents you from being able to deploy your software to any other platform by its interface.

Whilst provider lock in may not be a huge issue in itself, it does highlight the chief problem with Heroku… its a platform not a service. Being a platform method that Heroku controls every aspect of the deployment course of action – from where youre storing your data to how much resource usage you have.

This method that little problems – such as *always* having a subdomain obtainable for your app, paying PER APP (which can get very expensive), being unable to change your apps location, are a enormous issue.

Furthermore, Herokus deployment course of action is very stiff. This method that you cannot change things such as location, or already have multiple frameworks / platforms running under an application. Whilst it has buildpacks (which are very good) – they require you to hack together the various pipelines you may have into one central build course of action.

Because of these restrictions, many developers have cited the system as being effective as a staging ecosystem… but in many situations bad for production. Production environments require scalability and extensibility on a chief level (if you get traffic spikes, or are looking to set afloat in other countries – you need the ability to do it).

Whilst Heroku does have these to a degree, its without of granular settings makes it very difficult to justify using as a production service. This is amplified with the systems application-centric pricing structure.

The way around this is to ensure that youre able to use a system which is as flexible as required. Heroku may suffice in this respect for many beginner developers (who just need their app to run no matter what), for some seasoned developers (who may require a more individual system), the likes of cloud VPS sets tend to offer a more alluring ideal for production level web application provision.

leave your comment

Featured Posts

Recent Posts

  • 350 T15 An Phú Đông Q.12 TP.HCM
2,750.00$ (Fixed)
  • 350 T15 An Phú Đông Q.12 TP.HCM
9.98$ (Fixed)
  • Tĩnh lộ 8, CỦ CHI
5,400,000.00$ (Negotiable)
  • Thạnh Xuân 38, Phường Thạnh Xu...
108,000.00$ (Negotiable)

Recent comments