ChanceUSC said:vegetation said:ChanceUSC said:vegetation said:Stick with your hosting provider. For professional use, you're opening yourself a whole can of worms by hosting it yourself off a cable modem with no network redundancy. I'm not 100% certain that it is a cable modem, TWC is simply the reseller of this other company in my area. It has 2mbs up which is faster than a T1 and the latency isn't bad at all from what I've heard (I know a guy that is hosting successfully using it).
Of course it's a cable modem. They simply switch you to a higher bandwidth configuration and give you the policy rights of your new plan; you wouldn't even change anything at your end other than a reboot of your modem.
As I mentioned earlier, this is just bad news if you're doing professional services with customers expecting their sites to be up. You're playing with fire that something is going to blow up down the road destroying your credibility. Risk reduction is the way to go here, it certainly isn't costly. Heck, even I run a small commercial hobby site and I make more than enough on ads to recoup a $35/month VPS. I wouldn't ever consider putting my customers on a half-assed system and this is just a fun hobby for me that nets me no income.
The idea about reselling hosting plans mentioned earlier is a good one. It's what a lot of developers do.. Businesses will pay the money for a good site as long as it's reliable. Reliable is the key word.
No I agree that reliability is key, and I've done the reselling hosting plans too (which failed misserably, out of the last 3 hosts that I've directed clients too, there have been serious issues with and they are large / reputable hosts). The guy I know that runs a small 'host' off of the TWC business line in my area monitors his connection very thoroughly and has only noted a few minor outages that didn't last more than two hours over the course of a few years. The business class customers get a direct sales rep and the turnaround time between contacting his sales rep about technical issues and having someone on site to fix the issue is apparently really amazing in our area. I do agree with you guys in that I shouldn't be the one handling the emails because its one thing if a site goes down for a few hours, but its something completely different if emails start bouncing back.
I just have to make a decent run at this, I've got someone that is willing to invest 50k that i can spend on software licenses, hardware, and a more dedicated line if I can prove that I can get the business running over the course of the next year. I don't plan on putting more than 5 people on a line, infact I'm considering getting a business class DSL line that I can bridge incase 1 goes out..
More things to think about.
-Will you allow your customers to upload files? What if a file compromises your server security? Do you know enough about server permissions to prevent this? Do you understand SQL injection and do you know how to prevent it? If one of your customer's site gets hacked, all of your customer's sites are vulnerable.
-Believe it or not, I can hack many windows server setups, simply because they are not well thought out.
-Verizon Fios offers 15mbps up, 15mbps down for dirt cheap.
-Also consider running nightly backups.
-Do you have a hardware firewall? A nat router with port forwarding would actually be ok for this, unless it gets hacked.
-The box is strong enough to run all the software you want, but there is a reason people run them on separate boxes. Security. In an ideal setup, your web box would have 2 network cards. One for internal and one for external. It is the only computer that should get direct access to the internet. It will connect to the SQL server only through the SQL port on the internal card. This way, if your web server gets hacked or a virus..., your SQL data will still be very safe.
-I recommend Mailtrust reselling for exchange. I see many of my client spending lots more money than they should for exchange support. If they only went with a third party provider, they wouldnt need to spend on support. When you start supporting exchange, it may possibly take more time than you anticipate.
-4 GB ram is definately more than enough. 2GB should be more than enough depending on how efficient your code is.