The Open Source vs Commercial Software Application Intital Deployment Development platform debate is long over. If you have to develop web applications on a commercial platform, you might as well control the platform using an Open Source framework and avoid the license and maintenance fees from the commercial vendor altogether.

1. Comparison:
Percussion vs. Open Source Development Platforms
Intital DeploymentThe Open Source vs Commercial Software Application
Development platform debate is long over. If you have to
develop web applications on a commercial platform, you
might as well control the platform using an Open Source
framework and avoid the license and maintenance fees
from the commercial vendor altogether.
However, the rate of change on the web is rapidly
accelerating. To keep up, these highly customized
deployments (Commercial or Open Source) will require
constant re-integration of new modules and add-ons.
The ongoing development work needs to be budgeted
for and the effort required to support and maintain these
systems (in the form of developer cost, or a third party
support contract) must be considered as part of your
ongoing web strategy.
To breakthrough these roadblocks and eliminate time
and budget constraints, Percussion has transformed web
content management into a true product that is delivered
as a cost effective set of “apps” that add to what you already
have in place, while still providing you with the freedom
to build the strategic web applications that run alongside
your web content systems. By decoupling the content
management functionality from the overall web platform,
you have the ultimate flexibility—low up-front investment,
little ongoing investment in the content management
functionality, and the freedom to innovate on the web.
At right, we compare Percussion’s product approach
to the Open Source development platform approach.
Open Source
Development Platform
(Drupal, Joomla…)
Percussion
Deployment
Architecture
Coupled Architecture
The web server and the CMS are the
same server. Existing web servers must
be integrated or replaced to use the CMS.
Decoupled Architecture
CMS server runs independently, existing web
servers can be used “as is” and content and
functions are published to it.
Skills and
Technology
Developers build web applications inside
the CMS, and must learn each platform’s
architecture, APIs, markup language, and
code management best practices in order
to run and operate the solution.
Marketing and non-technical business users
create content and design in the CMS, while
developers build web applications outside the
CMS in any platform or framework of their
choice. Open APIs provide access points for
these web applications, but development is not
required to operate or deploy the CMS itself.
Implementation CMS functions are added by deploying shared
code, such as “modules” or “plug-ins” that are
then customized. The user experience of the
CMS is left to the developer who customizes
the modules or plug-ins.
CMS functions are deployed entirely as drag
and drop “apps.” The user experience of
the CMS is defined by the business user who
selects what apps to add.
Security Systems integrators take on the entire
responsibility for securing the deployment,
often requiring extensive “hardening” services
packages and support offerings.
CMS runs independent of the web server so
it introduces no new security thread vectors.
Existing security configuration for web servers
can be used “as is.” Allows systems integrators
to focus on customer facing value like site
usability and user adoption.
Performance Systems integrators must ensure high
performance operations, typically with added
services and best practices training, and added
support services, particularly as the site grows.
CMS runs independent of the web server,
CDN or other systems. Existing performance
configurations can be used “as is” allow
systems integrators to focus on higher value
areas like site usability and user adoption.
© Copyright 2013 Percussion Software, Inc. Continued ...

2. Open Source
Development Platform
(Drupal, Joomla…)
Percussion
User Adoption The user interface is custom tailored to each
implementation. Ease of use, workflow, and
overall complexity is up to the developers who
typically focus more on the resulting web site
than the users of the CMS. User adoption must
compete with web site functions for the same
implementation budget and time.
User interface is designed by Percussion to
maximize the number of possible users on
the system. Combined with out of the box
workflow, this focuses the entire CMS on
getting the most users onto the system and
the most content through the system out to
the web. This also frees the implementation
budget to be put entirely into web site
functions and other customer facing efforts
built outside the CMS.
Upgrades While minor upgrades are usually automated,
major new version upgrades typically require
complete re-implementation to use new
core platform features and modules. Added
implementation services need to be budgeted
for each major upgrade cycle.
All major or minor version upgrades are
handled the same way, and do not require
extensive re-implementation. Also, since
the CMS runs separate from the live web
site, upgrades are handled smoothly with
no impact on live web server.
Functional
Change
New functionality requires implementers
to download and add modules or plug-ins.
Modules minimize or eliminate new code
development, however added modules are
still new code to the implementation. Thus,
each change requires systems integration,
testing, backup and recovery and other
deployment processes when new code is
added to a software system.
Percussion is delivered through inter-
changeable “apps” layer, using widgets
and gadgets which are added automatically
through the version upgrade process. This
provides new functions in a black box manner
eliminating the need for code deployment
procedures and cost.
Extensibility
and
Customization
Developers write shared code against APIs at
various layers. This code must be tested and
deployed within the CMS.
Developers use Mashable web APIs to write
applications with code that resides outside
the CMS, either locally, or in still other third
party platforms.
Ongoing Use
Continued from front...
In all of the above situations, there is never a question of whether a system can provide a solution. Any approach
can be secure, high performing, and deliver top notch web sites with enough resources, time, and money to deploy
against the project. However, adopting a development platform means that you and your systems integration partner
are committing to become technology stack owners and developers, instead of direct consumers of new technologies
as they become available.
In Summary
The problem is not with open source. Open source does the
best job of giving you freedom to customize your own system
and minimize up-front development cost by sharing code.
The problem is with using any custom tailored open-ended
development platform for today’s constantly changing web.
Development platforms require significant budget dedicated
to system operations, and constant spending on services
that ensure the platform is correctly tailored and deployed
for usability, security, performance, and other success factors.
Further, as web change ensures a vast growing library of new
modules, plug-ins and other functions, a significant portion
of budget must be spent on upgrades, maintenance and
“reimplementation” to keep up.
With Cloud, mobile Apps, and open Web APIs leading
the way, Percussion believes the future for all web technology
lies in an ecosystem of independent technology consumers.
Whether Percussion is deployed in the cloud or on premise,
this trend toward pre-packaged “apps” allows Percussion’s
off-the-shelf WCM solution to focus entirely on the non-
technical content creators, the marketer and other
business users.
Percussion’s WCM product:
zz Plugs in immediately to your existing web infrastructure
zz Allows your web infrastructure to remain “as is”
zz Embraces the idea that our WCMS is only one of many
other web applications and technology services that make
up your web presence
zz Provides open APIs and free exchange of information
to maximize sharing and avoid any possibility of vendor
lock-in
Percussion’s approach allows spending to go directly
toward improving online interactions, scaling content, and
driving engagement to accelerate your business.
© Copyright 2013 Percussion Software, Inc. www.percussion.com