I just deployed a Ruby on Rails application to a production server in under 30 seconds. I didn't set up a VPS. I didn't install Nginx. I didn't configure a database. I didn't even touch a terminal on a remote machine. I just typed git push heroku master, and the magic happened.
This is Heroku, a "Platform as a Service" (PaaS) that is completely redefining what it means to be a "SysAdmin."
In the traditional world, you spend hours (or days) setting up your environment. You worry about OS versions, security patches, and library dependencies. Heroku abstracts all of that away. They use a concept called "Dynos"—isolated, lightweight containers that run your code. You don't manage the OS; Heroku does.
The workflow is beautifully integrated with Git. When you push your code, Heroku’s "slug compiler" looks at your Gemfile, installs the necessary dependencies, packages your app into a "slug," and distributes it to your dynos. It even handles database migrations and environment variables.
Need to scale? In the old world, you’d be ordering a new server. In Heroku, you just slide a bar in the UI or type heroku ps:scale web=2. Suddenly, you have twice the capacity.
# How scaling looks in 2009
heroku ps:scale web=5
# Scaling up to 5 dynos... done.
The price for this convenience is high. Heroku is significantly more expensive than a raw EC2 instance or a Linode VPS. And you lose a lot of control—you can't install custom OS packages or fine-tune the kernel. You have to follow "The Heroku Way" (which they’re starting to formalize as the "Twelve-Factor App").
But for a small team or a solo developer, the trade-off is a no-brainer. Heroku allows you to focus 100% of your energy on writing code and 0% on "mucking about with servers." It’s the closest thing to "Serverless" we’ve ever seen, and it’s making the "Cloud" finally feel like a reality instead of a buzzword.