PHP Application Server

For a long time, I've been thinking about performance issues in PHP. One of the things that distinguishes PHP from other web-dev languages, is that PHP architecture is build around the "share nothing" concept.  Practically, it means that whenever a user opens a request to the server, a new PHP process is invoked which retains a distinct "user-space" environment. No matter how hard you try, memory of one PHP process is never shared with another process. This allows the developer to focus on developing the app for one user at a time and not worry about scalability.


Application configuration and PHP - the basics

Every medium (or larger) application needs a bit of configuration variables, the only questions are the scale and the desire of the developer to spend more than a minute building it.

So lets make it quick.

I'm going to show 3 basic concepts of wide-system configuration storage with PHP.

Method 1: Plain PHP Array

This maybe the most simple and efficient method of all. Just keep your configurations inside a PHP array and use it globally across your app. Simple to use, fast to develop.


Automatic javascript generation on constantly changing websites

This time I will discuss something I wrote for myself.

The problem:

I'm (and maybe you are) constantly developing my application, adding features and closing bugs, both to PHP and Javascript pages. When it comes to PHP, there is no issue, we simply update the last version to the server and forget about it.
With Javascript, however, this is a bit more complicated.

Subscribe to RSS - PHP