Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Can I deploy apps on different machines with this? E.g. can I run my app on 3 servers with a load balancer?


sort by: page size:

Also check this from the webfaction site:

Scale as much as you need Our unique multi-machine load balancing solution allows you to manage your account on multiple machines from our control panel. You can easily deploy your apps on multiple machines and our system will automatically provide load-balancing between these machines. Some customers have scaled up their sites to tens of machines for a fraction of the price of dedicated servers.

I think that's the reason I signed up.. That and the prices.. It's nice to know you can scale out your solution that way.. but anyway, I still want to have a plan B if it doesn't work out with them.


Never heard of it but the product looks pretty compelling. Is there any provision for running multiple apps on one server instance?

Not if you need to use multiple app servers.

If you're only targetting 2-3 systems for redundancy (each the same apps), you could configure them exactly the sime behind a load balancer, then have each deploy just run to all 2-3. Did this as a POC early last year.

If you have the ability to spin up a new machine when the old one fails, and deploy your app onto it in one minute, it’s not a big leap to also run your app on two machines and avoid that downtime altogether.

Hi redguava, thank you for your input.

As you mention the app currently does allow you to run a multi-site setup, as well as a multi-company setup for those lucky people running more than one company.

Seeing the concern for 100% uptime I will be looking into offering as high uptime as possible, maybe adding some EC2 instances ontop of my Linode servers or something of the sort.

Thanks again!


Also, the OS abstraction would hide the multi-server aspect as well, so you could run the "OS" on a farm of machines, and your app would work fine even though it was developed on a single machine.

No, running multiple apps is fine. In fact, it's what Harbormaster does, it just helps you manage server deployments a bit more easily.

I assume you mean at work?

Yes, we'd have more than one instance of the app running. Ideally 3 or 5 instances. And they'd be load balanced. So I could update the app one instance at a time with no downtime. At least that is the goal.


Use multiple servers.

I don't know if it is possible to treat "Serverbörse" servers as cattle. They are all different. I know that k8s and Docker Swarm could in theory balance load between different machines, but never tried it in practice. But I had in practice some weird glitches with different CPU/motherboards/memory.

Also, comment I was replying to mentioned a 48 euro budget, it is a price of a single server.


Yes but it’s literally a single point of failure. You probably want at least two servers in separate physical locations. Also how do you do deployments without interruption of service on a single server?

also i think one should take care of Reliability into account as well, if you have only one app server it will fail - maybe eventually - and you'll find yourself trying to ssh into the server at 2am, have at least a few app servers load balanced, have 2 db servers replicating with auto failover etc..

Ever deployed desktop apps to 15k end user machines over multiple locations? I don’t want to do that anymore

A single powerful host can run a quite large business; you might put two identical instances of that host behind a loadbalancer to reduce downtime due failures or upgrades/deployments, and for a single pair of hosts complex orchestration is IMHO overkill, you can just manually run the deploy on one host, wait for it to start working properly, and then upgrade the other.

Beanstalk doesn't like having more than one virtual host per application/server/load balancer. You can do it but its a lot of custom code to make it work. Beanstalk does do deploys very well though with automatic deploys to a subset of instances, checking they are working, then deploying to a new set of instances. Big fan but it is really designed for one domain per instance set.

I think we could probably do it on 1 machine. We have multiple mostly for availability and handling spikes. There's definitely no reason we couldn't use 1 large machine to do this, just not a great reason to run a production app this way.

Wow, here's me thinking that you would have separate servers for database and web server and load balancers. Gives me faith.

Ok, but what if you want to run the same code on multiple remote machines (e.g. launch several deep learning simulations)?
next

Legal | privacy