Live data from Hacker News

Show HN: Build your own Heroku on your own servers

cloud66.com

101–110 of 110 posts

Re: Show HN: Build your own Heroku on your own servers

#101
post #99

Earlier quoted context omitted.

Where do you find sysadmins for high availability systems willing to work for $100K per year?

Depends on where you're living I suppose. In Chicago, a base of $100k/yr for a systems architect seems fair. In the Bay area and other areas that are more expensive, it will probably be more expensive, but I'm not as familiar with those markets. It certainly depends on the complexity of your product too.

ha. I was actually thinking of people I know in Chicago who charge huge amounts to admin trading systems.

Re: Show HN: Build your own Heroku on your own servers

#102

Earlier quoted context omitted.

Depends on where you're living I suppose. In Chicago, a base of $100k/yr for a systems architect seems fair. In the Bay area and other areas that are more expensive, it will probably be more expensive, but I'm not as familiar with those markets. It certainly depends on the complexity of your product too.

ha. I was actually thinking of people I know in Chicago who charge huge amounts to admin trading systems.

Ah, yes. Did my run in trading. Pay (and experience) is great if you have the stomach for it. I found it soul-sucking and ultimately left. You are correct though, trading is extremely lucrative, not even getting into the other benefits.

Re: Show HN: Build your own Heroku on your own servers

#103
post #56
post #37

Earlier quoted context omitted.

This is very cool stuff. Do you guys support (or do you plan to support) any type of cross-provider failover? I.e. if AWS goes down, auto re-deploy to Linode and handle the DNS re-routing, etc.?

Great point! Yes. We already configure DNS records for the stack (load balancers and servers). This allows us to take the same cut of code and build scripts and execute them against another provider like Linode or Joyent when AWS has issues automatically.

THAT is awesome. Is that feature live? How is the failover route configured?

Re: Show HN: Build your own Heroku on your own servers

#105
post #74
post #50

Earlier quoted context omitted.

Actually attended a local user group presentation on elastic beanstalk last night. Elastic Beanstalk not only handles auto scaling. You can set limits that enable it to launch a replacement server if your pages start responding slowly. The new console lets you easily add SSL certificates and schedule backups. I was pleasantly surprised how much Amazon has added to it in the last few years.

I confirm all this. Elastic Beanstalk is so good, I don't even touch EC2 anymore. All my webapps are now being deployed through it. It costs more due to fact that each environment needs its own load-balancer even if only one server is involved which is extra $18/month but it is still worth. If you deploy code that crashes webapp, just revert back to previous version. Problem fixed in a minute on all your servers. And…

I guess where we are attempting to be different is we are providing this functionality in a vendor agnostic way (ie. also for Linode, Joyent, Telefonica - Digital Ocean and Rackspace coming soon, and support for standalone servers in Hetzner, or your private cloud, or even under your desk for example)

As well as just supporting your preferred vendor (based on price, location, guaranteed location, SLA etc) it means that we can offer you a way to switch between vendors if that vendor has some down-time, or doesn't meet your changing requirements as you move forward.

Also, we are really trying to be as application centric as possible - everything stems from your application code - and then provide the ongoing management tools you need on top of that (for easy scaling, backups, scheduled tasks, migrations, reporting etc)

Great feedback from everyone! We didn't get a whole lot of sleep last night!

Re: Show HN: Build your own Heroku on your own servers

#106
Not having looked at this extensively I don't see what about it is more compelling then just using my own servers with git-deploy or a similar infrastructure. If i am going to run Ops i want to run Ops. If I am going to outsource it I want to outsource it. This seems like a middle ground that doesn't add too many compelling features to the party.

Re: Show HN: Build your own Heroku on your own servers

#107
Just looking at the stack docs put me more in mind of Engine Yard than Heroku: HAProxy, nginx, passenger, DB options etc.

And that's a good thing. I realise Heroku is devsexy but having compared the two for a serious production app for bigco (a contest that EY won hands down) this architecture is long-term more resilient and adaptable.

So to me it's a sort of Engine Yard, BYO VMs. Ok. What is that, Devops as a Service? Nice look, btw.

Re: Show HN: Build your own Heroku on your own servers

#109

Just looking at the stack docs put me more in mind of Engine Yard than Heroku: HAProxy, nginx, passenger, DB options etc. And that's a good thing. I realise Heroku is devsexy but having compared the two for a serious production app for bigco (a contest that EY won hands down) this architecture is long-term more resilient and adaptable. So to me it's a sort of Engine Yard, BYO VMs. Ok. What is that, Devops as a Servic…

DevOps as a service, WebOps in the cloud or anything you'd like to call it. We made it because we had the same issues as all other devs with Heroku. I hope we built something useful.
Post reply on HN