|Should I convert from ASP -> PHP?|
Should I switch from Asp to Php?
I have an e-Commerce website with MS-SQL as my backend.
On top of the online catalog, I have about 100 additional ASP pages.
I am sort of looking at PHP ‘cause everybody tells me I should be on a Unix platform.
Every hosting company that I have used always tells me that Windows/ASP is a bad combo. (You know a drain on resources)
I wouldn't switch.
And Windows/ASP runs natively on Windows servers. Bad code is a drain on resources.
Hosting companies provide both, and salesmen will tell your whatever it takes to get your business.
I use Windows/ASP/mySql without problems and wouldn't switch.
There are only three reasons I can think of for switching;
1) You need a service that's cheaper than your current ASP+MSSQL host to the point that it's noticably eating into your bottom line.
2) You are having reliability issues with your current ASP solution that aren't easy to address using some other means.
3) You have long term plans that require PHP.
If you don't have a really good reason I'd say "If it ain't broke don't fix it"; it will cost time and money to recode a site between languages, and there's also a risk of extra bugs creeping in as things are re-implemented.
Learn from the experience and create the next one in PHP.
From personal experience: Going from MS-SQL to MySQL would be a giant step down. Depending on what your doing, you can expect MySQL to slow dramatically after 500,000 records or so...
|1) You need a service that's cheaper than your current ASP+MSSQL host to the point that it's noticably eating into your bottom line. |
When you look at the cost of the hosting provider, you need to look at more than just price. Sure, you can pay $7/month for a nice *nix host. But do they have good tech support? Do they have a phone number to call, or at least have a reliable support email address? I pay $11.25/month for my Windows 2003 host. This gets me a 35mb SQL database too (99.9% of the time, more than enough). They provide all (included in the price) the awesome ASP tools, that make my life easier: ASPImage, ASPTear, ASPUpload, ASPEmail, etc. They have an outstanding control panel that lets me have hands on for my email accounts, front page extensions, ftp accounts/access, bandwidth usage, site stats, etc., etc., etc. The only thing I can't control is file permissions. But my tech support is on top of the ball, every single time. Not once can I think of a time they did not meet/exceed expectations.
I'm not saying you need to go with my host, I'm just giving you things to look for, when choosing what you need. Don't just see the lowest price and run with it. Do some research, talk to other people here at WebmasterWorld, find out who they like/use, then make your own educated decision.
The main arguments that I agree with have already been said: "If it ain't broke, don't fix it", and "Bad code drains resources". If your bottom line is hurting, at least make sure you take the necessary long term steps to make sure you aren't just going to hurt it more.
My 2 cents.
there are some people for whom the answer is
always "it's better on 'nix"
this is not always true. i just had someone
walk away from the only solution that was going
to work for him, because his admin was whining
about leaving 'nix. meanwhile, his bandwidth
is spiking big time without the solution.
did his admin have an alternate solution? no,
but a least he got to stay with his toys.
bottomline line is, you should do what's good
for your business. all other considerations are
secondary. including what your advisors deem
btw, if someone says "open source", it presupposes
that someone has the skills to actually modify
the code to correct a deficiency. that is really
rare and truly expensive.
From my PubCon notes on tedster's presentation:
"backend choices should not be by default"
Which I took to mean that one should choose the right solution for a particular problem. In some cases it might be *nix, in others windows.
We're looking at doing some things on a asp.net platform. It looks pretty cool.
I agree very much that the choice of platform and development language should be based on requirements.
But, if you are going to switch anything I'd higly recommend looking at the .Net Platform. The interesting thing about .Net is that there are initiatives to port the framework over to Linux. Check out [go-mono.com ] for more info. When they are successful at completing the port you can have best of both worlds.