5 ms·

There’s been a bit of a full circle going on in the industry. PaaS like Heroku were rejected by many because they couldn’t tinker inside the box. Docker and

There’s been a bit of a full circle going on in the industry. PaaS like Heroku were rejected by many because they couldn’t tinker inside the box. Docker and Kubernetes changes that, and there will be new Heroku-like experiences built on them. But for now we are in this weird mode where the Kubernetes momentum is eclipsing even Docker, even though raw K8s reminds me of Linux in the Slackware days. there is so much FOMO, people don’t consider Heroku or anything off the Kubernetes wagon, except maybe AWS Lambda.

collyw 8y ago
As someone that knew how to set up a server before hand I found Heroku a real pain in the arse to use.
- acjohnson55 8y ago
  To learn, or to utilize on an ongoing basis? I'm curious what you found difficult, because since remapping my mind to 12-factor years ago, I still haven't found anything as simple as just using Heroku.
  - collyw 8y ago
    I only used it once or twice, so to learn. Every time I have had an EC2, Rackspace equivalent or other server I knew what I was doing and other than what felt like some minor stuff. I guess its kind of related to the comment that people didn't like not being able to tinker with the box. (It kind of felt like a black box to me, far more difficult to debug than a "normal" server).
    - parasubvert 8y ago
      A lot depends on where and how you work. If you are responsible for development and end to end operations down to the VM, K8s and Docker make a ton of sense. If someone is doing that for you, ie. roles are separated, or you don’t want to take it on and prefer to outsource it, then a higher level abstraction like Heroku makes more sense. Debugging is different (still possible, just different from if you owned the full box). This split also accounts for why AWS Lambda is growing in popularity (and debugging is probably its main gating factor).

collyw 8y ago

As someone that knew how to set up a server before hand I found Heroku a real pain in the arse to use.

acjohnson55 8y ago
To learn, or to utilize on an ongoing basis? I'm curious what you found difficult, because since remapping my mind to 12-factor years ago, I still haven't found anything as simple as just using Heroku.
- collyw 8y ago
  I only used it once or twice, so to learn. Every time I have had an EC2, Rackspace equivalent or other server I knew what I was doing and other than what felt like some minor stuff. I guess its kind of related to the comment that people didn't like not being able to tinker with the box. (It kind of felt like a black box to me, far more difficult to debug than a "normal" server).
  - parasubvert 8y ago
    A lot depends on where and how you work. If you are responsible for development and end to end operations down to the VM, K8s and Docker make a ton of sense. If someone is doing that for you, ie. roles are separated, or you don’t want to take it on and prefer to outsource it, then a higher level abstraction like Heroku makes more sense. Debugging is different (still possible, just different from if you owned the full box). This split also accounts for why AWS Lambda is growing in popularity (and debugging is probably its main gating factor).