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

Access Control

Access control is about controlling user flow within your application. Do not mistaken access control with security which is a bigger subject in itself. Access control begins by authenticating user and limit his or her activity in your application. An activity is something like creating, updating or deleting a content. There are always finite number of activities that can be done in a given application. Each user can be assigned to a set of activities that he or she is allowed to do. Access control is usually tied to session management. However, you do not need session management to have access control. When a user log in, a session is created so that the user is remembered for the subsequent access. Otherwise the user has to keep on providing his or her credential for each access. We can also keep a list of activities that the user is allowed to do in the session record. Some applications let the session alive indefinitely and some applications time out user after a duration of inacti...
Post a Comment
Read more

Separation of Front-end and Back-end Concerns

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts....
Post a Comment
Read more