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

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

Sending Emails via SMTP

msmtp  requires a minimal setup for sending emails via SMTP compared to sendmail. Here is a configuration for you to send emails from a web host to an external SMTP server. Prior to doing that, you must check whether there is a clear communication channel between your web host and the SMTP server. You can use Telnet . Set up msmtp You are going to set msmtp as an MTA . Hence, you need to remove all other MTAs such as postfix and sendmail: $ sudo apt-get --purge autoremove postfix sendmail Install msmtp and related utilities: $ sudo apt-get install msmtp msmtp-mta mailutils Configure msmtp: $ sudo nano /etc/msmtprc # Set default values for all following accounts. defaults # Use the mail submission port 587 instead of the SMTP port 25. port 587 # Always use TLS. tls on # Set a list of trusted CAs for TLS. The default is to use system settings, but # you can select your own file. tls_trust_file /etc/ssl/certs/ca-certificates.crt # The SMTP server account mx host mail.mx.example

fatal: Couldn't find remote ref master

If you are using Github then  master is now known as main . Whatever you want to do with a master must now be referred to a main . If you search for this error message on the Internet then you will encounter with a lot of old discussions on how to set up your master properly which is probably not what you are looking for. The master  is your problem. Rename it to main . I wrote Git My Way about two years ago. Today I created another Github repository. I got this  "fatal: Couldn't find remote ref master"  error message when I wanted to sync the new repo for the first time with my notebook using the notes I wrote in the blog. All the discussions around the error message I found on the Internet were perplexing. Then I recalled that Github had renamed master to main  due to the master-slave connotation. We always have a master copy of a code, never a slave copy. Now suddenly a word context has been diminished for good. What is going to happen to the existing vast documen