4 ms·
I can't deploy Kafka to Heroku. I can technically deploy Akka but 1X/2X instances aren't going to cut it and PX dynos are hilariously expensive, plus clusterin
by saryant 12y ago
I can't deploy Kafka to Heroku. I can technically deploy Akka but 1X/2X instances aren't going to cut it and PX dynos are hilariously expensive, plus clustering isn't possible.
Yeah, if your app can fit on Heroku, leave it there. But Heroku is not a silver bullet for all types of apps. Containerizing them makes it much easier to add and remove instances, easily deploy new services, move instances around as underlying resources die, etc. Docker doesn't provide everything to make this happen but it's the key.
I've spent the past two weeks moving an Akka cluster into Docker with CoreOS. I'm about to deploy Kafka in the same way and so far it's been fantastic.
- icebraining 12y agoI can't deploy Kafka to Heroku But you couldn't before either and yet Heroku still existed, so how does that make Docker an Heroku-killer?
- saryant 12y agoFair enough. My point is that Docker makes packaging up the various services I need to deploy much easier and more predictable. Now, rather than spin up three EC2 nodes to be Kafka instances, I just use fleet to submit three Kafka units and it finds available resources among my existing CoreOS cluster. If I need more capacity, I spin up more generic CoreOS instances on EC2 and fleet starts using them. The groundwork is being laid and I think we're going to see a lot of competition in Heroku's space. Given the price difference between Heroku and EC2 (much less DigitalOcean) I think there's a lot of profit margin for competitors to attack. That's Heroku's weakness: it's easier than ever to build the equivalent functionality.