Differences between Rackspace Cloud Sites and a traditional web hosting environment
The Rackspace Cloud Sites environment differs from a traditional hosting environment in the following ways:
More than one server serves a specific website’s request because the load balancing capability is made available to all websites. Depending on file extensions, the load balancer directs traffic to appropriate servers.
Subdomains are treated as full websites.
The operational architecture of Cloud Sites uses a caching mechanism for media content and ASPX requests. As a result, some updates might not take effect immediately.
The databases needed to host a site are usually on different virtual machines and users can provision them through the control panel. They must provide the hostname and not the localhost in the database connection string.
Updating content by using FTP is different in the sense that only certain directories are accessible and the FTP address is determined by Cloud Sites. An account holder cannot upload files to a client’s directories.
By default website statistics and raw logging are turned off. Users must explicitly enable them if needed. By default, PHP and cron job task logs are written to the logs directory.
Continue the conversation in the Rackspace Community.
©2016 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License