Skip to main content

Exit Shared Hosting Early

As a programmer, I would like to advice all web programmers to exit shared hosting as early as possible. But please take my advice from a technical point of view, not the business point of view. Shared hosting will go away and will be replaced by cloud computing. Re-acquire your programming skill towards cloud computing. See my other post on Why I Chose the Programming Languages.

Ten years ago there are 360 millions Internet users. Today, the Internet has 1.7 billion users, which is 4.7 times more users than a decade ago. And 10 years ago the bandwidth for the Internet access was relatively narrower than the generally available broad bandwidth of today. And today more people are accessing the Internet via mobile phones. Thus today, the Internet traffic is obviously many folds more than a decade ago.

Shared hosting was good when the Internet was small and when the traffic was relatively friendlier. Your website will either have visitors or none. When it will have visitors the traffic will be huge. Now any shared hosting server will not be able to cater for your website traffic. When your website load very slowly your visitors will go away.

Don't even think to move your website to a dedicated server when the time come. You will not have the time window to move your website to a dedicated server because your visitors will move away faster. And what make you think a dedicated server can cope with your website traffic? Looking at the Internet rapid growth a server is not enough for a website. You need a cluster of servers and mirrors. Where can you get those if not from cloud computing?

Forget about physical server and operating system. Start learning about how application scaling works. Learn how to scale your software and how to scale your data. Google App Engine is a good place to start.

Comments

Post a Comment

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr...
8 comments
Read more

Using React in Foundation for Sites

This post was the precursor to the Foundation-React Template . React and Foundation are two different web UI frameworks addressing different needs. They evolve differently. Both of them are powerful on their own accord. Fusing them together may create superpower. We will walk through the process of adding React into Foundation. We will start by installing both Foundation and React through command line interface (CLI). Then we will create a simple Todo web app. Along the way we will highlight the development process. But before all that, let us summarize React and Foundation. The details can be found at their respective websites. Both of them are well documented. React is a run-time UI rendering engine. It renders dynamic UI elements in its own fast virtual DOM, and only update necessary changes to the slow browser DOM. This behaves like a  double buffering DOM which makes any UI update feels fast. React wraps a UI rendering script in a component. A React component can ...
Post a Comment
Read more

Debugging PHP using Apache Error Log

PHP runs on the server side and behaves like a function that return a value against the given arguments. A remote client may call this function and expect a specified return value and nothing else. So how do we debug this function ? It must not return debugging messages since the client is never designed to handle them. We must never burden any client to handle debugging messages. If we run PHP through Apache server then we can use the error log to keep our debugging messages. It may not be the best way to do it. But we only want to talk about this approach now. Error Logs The Apache error log files generally can be found in the following directory: var/log/apache2 We issue the following command from within the directory to read the latest error messages: # tail error.log The tail command reads the last few lines from the error.log file and prints them on the terminal. If we need to read a specific number of lines from the end of the file then we can specify the -n opti...
Post a Comment
Read more