Brandon Tate of Appnovation writes, "Here at Appnovation, we frequently use the Acquia hosting platform for our clients. The Dev Cloud and Managed Cloud are impressive platforms that fit well for many Drupal sites being built today. I’ve listed some items below that have helped with the overall build quality and ease of use for these platforms."
When I saw the headline of the Forrester article proclaiming the death of the enterprise CMS suite, I couldn't help but both be pleased with myself, and feel a little sorry for the analysts. After all, I scooped them and proclaimed the exact same thing a little more than three weeks before.
Forbes discusses Drupal as a powerful force in the tech world and Acquia's commercial support of Drupal through subscription services for learning and productivity tools, cloud hosting, social business software, and more.
Legacy CMS vendors, like OpenText/Vignette and Autonomy/Interwoven, are experiencing the effects of a disruption of their marketplace. As a result, many organizations are flocking to open source. CMS Wire says that "Acquia seems to understand the current trend to push this out of the hands and heads of the overburdened IT operations shops and into the cloud at large."
Tech Target features Chris Brookins, Acquia VP of Engineering and Product Management, in a discussion about cloud computing, open SaaS and PaaS, and vendor lock-in following the Mass Technology Leadership Council's Cloud Computing Summit.
Phase2 Technology will be teaming with Acquia and Mediacurrent to provide development and hosting support in the transition from Vignette, the Georgia Technology Authority's current enterprise content management system.
Acquia's Jim Shaw discusses the cloud and that today’s web applications face very real challenges to deployment. Websites are incredibly content rich, highly dynamic, and subject to massive swings in load because of anything from content gone viral to the death of a celebrity.
Today's web applications face very real challenges to deployment. Websites are incredibly content rich, highly dynamic, and subject to massive swings in load because of anything from content gone viral to the death of a celebrity.
Putting a CMS in the cloud addresses the scalability issue--at least, in theory. The cloud must be optimized for the application to get its full benefit. It doesn't matter that three servers are ready to catch extra traffic if they're not configured to do so. Further, a cloud platform that's not configured to match the CMS's particular needs will have to work much harder than it needs to, resulting in higher loads than is really needed to serve the traffic. For example, it makes sense to cache static content: But will the cloud be able to tell the difference between a user who's signed into the application (and therefore receives dynamic content) and one who isn't?