We've had a shared server for $8 a month, and then a dedicated server for $165 a month. While the shared server now acts as a development area, and is struggling to handle our database load (we often get knocked out due to cpu hogging), the dedicated server is simply a hole in the pocket (given the small size of our pockets) - even though its performance is dependable.
So what seems to be the solution? Instead of going for a VPS (Virtual Private Server), we decided to host our own server. This way, we'll own an asset, and will not just be leasing equipment.
Ofcourse, once our website requires more robust hardware (failover servers, separate database servers, hardware firewalls and such), we'll have to go back to professional server managers.
Soon we'll be getting a Dell Poweredge T100 running Ubuntu Intrepid Ibex.
Surprisingly, this server was a steal at its price, and should pay for itself in 3 months flat.
We will share our home network with this server for the time being (and set our routers to give it priority on bandwidth). Once the network requirements go up, we'll either go to a rack space provider or get an internet connection for the server.
What about the static ip? We're going to shoe-string it here as well. To avoid the cost of static ip, we'll use a service called dyndns which ensures our url always points to our server's ip address - even if the server ip changes.
Lets hope this is wise cost saving, and doesn't hurt us in the long run. The risk is definitely high given I'm the admin!
So what seems to be the solution? Instead of going for a VPS (Virtual Private Server), we decided to host our own server. This way, we'll own an asset, and will not just be leasing equipment.Ofcourse, once our website requires more robust hardware (failover servers, separate database servers, hardware firewalls and such), we'll have to go back to professional server managers.
Soon we'll be getting a Dell Poweredge T100 running Ubuntu Intrepid Ibex.
Surprisingly, this server was a steal at its price, and should pay for itself in 3 months flat.
We will share our home network with this server for the time being (and set our routers to give it priority on bandwidth). Once the network requirements go up, we'll either go to a rack space provider or get an internet connection for the server.
What about the static ip? We're going to shoe-string it here as well. To avoid the cost of static ip, we'll use a service called dyndns which ensures our url always points to our server's ip address - even if the server ip changes.
Lets hope this is wise cost saving, and doesn't hurt us in the long run. The risk is definitely high given I'm the admin!
Posts
No comments:
Post a Comment