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.
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.
This summer I worked at Acquia building status updates and activity streams in Drupal. The modules I developed became the centerpiece of Commons 2.0, which was released on August 31st. This new major version of Commons represents a giant leap forward in the world of social business software. It introduces a familiar, easy-to-use communication interface into a realm previously burdened by its focus on static documents.
Yesterday, Mozilla announced a new initiative called BrowserID, which is an easy, secure way to log in to websites without having to remember your password for each individual website. So last night I wrote the BrowserID Drupal module, which lets people log in to Drupal websites using BrowserID.
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?
SaaS vendors are looking to lock customers in to long term contracts with no exit strategy, says Jim Shaw, who argues that a new model, OpenSaas, could be the answer.
One of cloud’s best kept secrets is the lack of portability for applications delivered using the Software as a Service (SaaS) model. Many resellers help companies sign up for SaaS applications with the belief that it'll be easy for them to migrate to another if they need to. But that runs against the plans of the SaaS vendors, who look for long-term agreements to lock customers in by providing no exit strategy. A new model, called OpenSaas, is the answer.
Acquia's Bryan House, VP Product Marketing, discusses OpenSaaS and its ability to enable organizations to focus on their core competencies, without sacrificing control over the web experiences that propel their business.
I posted a news blog earlier this month concerning some high profile adoption of the Drupal open source Content Management System (CMS) -- or to use Drupal's preferred description, "The free and open source software package for publishing, managing and organising a variety of content on a website."
With Drupalcon London coming up this August and with the interest that story received I feel it is justified if we revisit the topic with some comment from the commercially-backed spiral arm of the Drupal galaxy.
... and the name you are looking for here is Acquia.
Woburn, MA - June 2, 2011 - Early this past May, co-founder and CTO Dries Buytaert of Acquia, a provider of commercial open source, social publishing solutions for Drupal, shared his insights for web-based business owners, developers and marketers on Drupal in the Enterprise at the 2011 CMS Expo Learning and Business Conference.
CMS stands for content management systems, which are platforms that we use everyday, either built in-house to manage company workflow or well-known platforms like WordPress, which are used by most online publishing sites (like this one). Intrigued by Buytaert’s thoughts on open source’s potential for disruption, I reached out for an interview to discuss 5 reasons why open source will shake the CMS establishment industry.