I was recently at a networking event where I got chatting to a founder of an Internet of Things consultancy company. We had very similar views about the confusion around cloud services – at the moment IaaS is the default choice (it doesn’t even have to be explained), but is this the best option?
This got me thinking, what are senior decision makers, or buyers, looking for with a move to a cloud platform. If buying decisions are being driven by a CIO then it’s probably going to be cost savings. This makes perfect sense; if you have ephemeral computing requirements then of course you should benefit from the race to the bottom between the big public IaaS providers.
Platform as a Service is the least defined and smallest (annual spend) layer in the “* as a Service stack” despite being a growing market, but this is changing. Venturebeat explain the cloud layers well if you need a refresher – http://venturebeat.com/2011/11/14/cloud-iaas-paas-saas/.
Graph data from: http://www.idc.com/getdoc.jsp?containerId=prUS24298013
IaaS and SaaS dominate the market and are well understood. Use Google Apps or Salesforce? Then you’re using SaaS. Bought a virtual machine from a ‘cloud’ supplier? You’re using IaaS! The big gap is PaaS.
Now we’re seeing the same repeatable pattern of growth and development from the IaaS world in PaaS. Open-source projects are developing existing technologies (see Docker and LXC), then major vendors absorb / package / develop those technologies into (sometimes open source) off the shelf stacks. The big players are RedHat with OpenShift, and Pivotal (spin out from EMC and VMware) with CloudFoundry.
Think back to a maturing IaaS market before we began the race to the bottom we’re seeing now. If you wanted IaaS or API driven infrastructure then you’re buying public cloud.
When you install WordPress you need to edit your
wp-config.php file to setup a database connection. If you scroll down further in this file with your favourite text editor you will find a line named
$table_prefix = 'wp_';. This is the prefix for all the tables that get created in the database when WordPress is installed and used.
The prefix is important when using a single database for multiple WordPress’. A different prefix for each instance of WordPress will prevent clashes when saving and serving content from your site.
It is easiest to pick a prefix, or leave the default and be happy with that. However, there are some situations that require the table prefix to be changed.
- You may be consolidating WordPress installations and require a single database to be shared between multiple instances.
- Setting a non-default prefix can add extra security from ‘script kiddies’.
- Maybe your site has changed and the prefix is no longer applicable – it will make it easier to manage your DB with a prefix which reflects the name of your site.