SaaS WCM Architecture Allows for Massive Parallel Development
Perhaps the most important business problem Crownpeak solves is enabling massively parallel development for large organizations with many websites. Picture a large organization with 100+ web projects. Every one of those projects needs to evolve on a regular basis. Unfortunately, the centrally managed web content management service delivered with last-generation products like Interwoven, Adobe, Tridion or SharePoint create a terrible bottleneck to evolution and new project development. The centralized, monolithic approach to web content management is a failure.
The problem is the software architecture of the last generation of products. A developer who makes an error can bring down every web site across the organization. A developer could access or expose sensitive data or release insecure code. Therefore, every change must be run through a carefully controlled software development lifecycle. That takes time and discipline.
If dozens of different development teams were set loose on the central WCM system all at once, there would be chaos. It would be impossible to keep the system stable, reliable and secure. That’s why every single large organization with dozens or hundreds of sites on a last-generation platform fails to be agile in the web environment.
Crownpeak has created a unique software architecture to enable massive parallel development. We had to in order to deliver a scalable, globally managed SaaS. Today, hundreds of sites are being implemented on our platform simultaneously as I write this note.
Massive parallel development is possible with Crownpeak because the template environment is completely separate from the core application, database and content repository. This also makes it possible for any web development company to implement projects on the Crownpeak system – the level of development to get a project live is much simpler.
With our architecture, it’s not just possible, but common for large organizations to have dozens of projects, all with separate development teams, created, modified and launched in parallel. The requirement to run a software development lifecycle across the entire platform goes away. The requirement for the teams to coordinate and synchronize activities goes away. QA is still required, but it is specific to the project and no QA is required for the platform itself because the platform never gets touched.
When global organizations standardize on Crownpeak, they are able to say to the site owners, “Here are the keys to the kingdom. Please make whatever changes and launch whatever projects you like. But please also follow these guidelines.”
With Crownpeak, the central organization evolves to on that creates, enables and cross-promotes functions across the organization. It’s normal for the central organization to add a range of additional SaaS functions, pre-integrated and offered to the disparate lines-of-business and markets over time. Crownpeak supports over 40 different integrations with best-of-breed marketing product partners today and that number is continuing to grow.
It’s not enough to have a great central website. The regions, divisions, lines-of-business and markets around the globe must be given the tools to be successful and that’s what Crownpeak enables and what no on-premises product can.