The constant battle a web site administrator must fight is the resource requirements of their site in contrast with the resource requirements of the configuration it is run on. In the end, this will almost always dictate how many user requests can be handled at any point in time. A common tool in the arsenal to fight this battle is to find clever ways to off load these common, or static, requests, off the server and allow it to spend as much time as possible delivering dynamic content as quickly as it can handle. This allows a server to not handle more request than before, but leaves it free to address more than previously it would have.
Deploying your application or web site can be a difficult process. In most cases, it involves multiple complicated steps, a long documentation process and constant emails to tell your team what was deployed. It’s also a very manual process, prone to mistakes or errors. That’s why having an automated process to deploy your application is critical.
A question that we get here at Rackspace is, “How many servers do I need to handle all my holiday traffic?” It is a pretty difficult question to answer because of all of the different variables. Because of the cost-effective nature of the cloud, one answer might be to overprovision and have extra resources to make sure that you site can handle a large amount of traffic. However, there is another way that not a lot of people think about: serving your landing page off of our Content Delivery Network (CDN).
Joomla is one of the most awesome pieces of software out there, and there are four main reasons that it excites me and why I continue contributing to the Joomla community and an advocating for this CMS.
Often times Rackspace customers and potential customers ask me about the best way to stream video on their Joomla site. This depends on how many users they plan to stream the video to along with how large the file might be. These are some of the technical considerations that you need to think of before mapping out your Joomla environment.