How to prevent website to crash

Question

0.00/5 (No votes)

See more:

Hi guys... i'm developing a website using php and im aware that im just a newbie when it comes to this page and someone just said that when my website start to have traffic the website could crash... so i was wondering what are the do's and dont's on creating a dynamic website... For example i have this 2 page... the first page is this:
action.php
-> This only contains a form to be displayed (new category form). Now on this form i'm calling a page namely update.php

update.php
-> update.php contains this code

switch($action){
case 'new_user':
			
$values= array("action" => "insert",
	"table" => "mytable",
	"column" => "",
	"values" => "''" . ", " .	
	quotedstr($_POST['user_desc']) . ", " .
	quotedstr("0") . ", " .
	quotedstr(isset($_POST['can_post_blog']) ? "1" : "0") . ", " .
	quotedstr(isset($_POST['can_sell']) ? "1" : "0") . ", " .
	quotedstr(isset($_POST['page_misc_profile']) ? "1" : "0") . ""
	,
        "where" => "",
	"specialStatement" => ""			
	);
			
	$output= updateQuery($values);
	break;
default:
	$output="no";
	break;
}
echo $output;

as you can see on my update.php im not using any class or extending of class or whatsoever... will this add to the possibility that my site will crash? i dont know what should be the best approach...

Posted 19-Feb-12 14:22pm

Madzmar25

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-02-20T09:22:00

There are few unrelated issues with that. The "Web site" cannot crash otherwise an HTTP server crashes which does not really happen, maybe extremely rarely. What could happen is that your PHP code throws an exception when a HTML page is being generated.

Here is the problem: a site PHP settings should be tuned the way the unhandled exception is never shown during production. Some Web hosting providers violate this rule just because people working with this site are illiterate. At least, I faced with such situation once. This is intolerable failure; if this is the case, you should either make your provider to do it right or leave the provider as soon as possible. Ideally, you should have two separate sites: one for development and internal testing, another for production. The internal development side can use both options: to hide all exception handling if you have them unhandled in your code, or show them for debugging purpose. The production server should always hide unhandled PHP exception.

On the development side, you should not let unhandled exception. You need to handle all exceptions on the very top of the stack of your code. As to catching and handling exceptions anywhere in between, you should keep catching and handling exceptions to the absolute minimum. One of such exclusions is: sometimes you need to catch low-level and general exception, use exception information to create a semantic exception explaining the problem in more semantic terms and provide semantic exception information and throw this new exception.

If there is an exception you did not expect, you can log exception information (for example, in a special file which you should never expose), to investigate the problem later.

This can be helpful:
http://www.devshed.com/c/a/PHP/Logging-With-PHP/[^],
http://www.stanford.edu/dept/its/communications/webservices/wiki/index.php/How_to_perform_error_handling_in_PHP[^],
http://www.stanford.edu/dept/its/communications/webservices/wiki/index.php/How_to_create_logs_with_PHP[^],
http://confluence.arizona.edu/confluence/display/WEBPRACTICES/PHP[^].

—SA