Professional Documents
Culture Documents
BLOGS
Jason Smith
Chief User Experience O6cer
W hen building your best-of-breed digital experience platform (DXP), choosing a CMS that lays a
solid foundation is crucial. The enterprise CMS market, however, is vast and overwhelming.
That’s why you need to narrow the options down to speciPc technologies that are well-suited to content
management today, as well as in the future.
In 2019, Java is still the second most popular programming language, second only to JavaScript, and
that means a large talent pool of developers, a wealth of community knowledge, and a multitude of
quality tooling. A Java based CMS, therefore, is ideal for enterprises seeking scalability at lower costs
and familiar technologies. Let’s look at what a Java CMS is, the primary benePts to a Java-based CMS,
and how to choose the best Java CMS.
When it comes to enterprises in particular, a Java-based CMS is ideal because the Java language has a
long history of being used for enterprise-grade software due to its reliability and stability.
2. Familiarity
At the enterprise level, companies are likely using some Java-based software already. That means their
development teams will already be familiar with the language and its tooling. Even if your company
isn’t using Java, there’s a larger availability of developers to hire than other, less popular programming
languages. The familiarity of Java, therefore, can reduce the time to market and overall total cost of
ownership for implementing a Java-based CMS.
3. Integrations
For most companies, integrating their CMS with other applications like CRMs, ERPs, and marketing
automation tools is critical. Luckily, the Java community has speciPed a standard for modularized
software called the Open Services Gateway initiative (OSGi). A Java-based CMS, therefore, can take
advantage of standards within the Java ecosystem to make integrations with other enterprise software
more straightforward for developers.
4. Security
Java - with its Java Virtual Machine (JVM) - is generally more secure than other programming
environments. That’s because Java code is compiled into bytecode and runs on the JVM in a sandbox-
like environment instead of directly on the server. Java also handles memory management for
developers and other low-level tasks. These factors reduce the opportunities for exploitation when
Java software is deployed into production.
5. Platform Independence
The Java language, and in turn, a Java-based CMS has the cexibility of being compatible with any
server that can run the JVM. This means a Java-based CMS can be deployed on Linux or Windows
machines - both of which are commonly used for enterprise infrastructure. The cross-platform nature
of Java, therefore, saves the cost of investing in speciPc hardware to run a particular CMS.
6. Easy Deployment
Along with platform independence from a hardware and operating system standpoint, most Java-
based CMSs can run on a variety of application servers. That’s because most Java CMSs can be
deployed as a WAR Ple that’s compatible with application servers that most enterprises use like
Tomcat, WebLogic, and JBoss. This lets companies deploy the software within their existing Java
environments.
7. Scalability
Scalability is critical at the enterprise level, and that’s why many Java-based CMSs leverage J2EE stack.
The J2EE architecture makes scaling horizontally and distributing workloads across clusters of servers
easier. The cexible deployment options for Java-based CMSs also means they can be deployed in the
cloud for even greater scaling capabilities. With cloud services like Amazon EC2, new CMS instances
can quickly and automatically be deployed when necessary.
At dotCMS, we have an “everything as service” philosophy that means the out of the box REST APIs are
highly robust. Using these REST APIs - or the latest GraphQL API - it’s easier than ever to connect and
interact with other applications. Developers and even non-technical users can even create additional
endpoints using lightweight Velocity scripting. If there are deeper integrations necessary, or the third-
party system doesn't expose APIs, then developers can use OSGi plugins.
With dotCMS, developers can use OSGi plugins to build new functionality. OSGi plugins run in isolation,
so there’s a reduced risk at impacting the dotCMS core when they’re deployed. Furthermore, if there are
highly speciPc business requirements, then the dotCMS source code can be modiPed because it’s
open-source.
Ensure Marketer-friendliness
While choosing a Java-based CMS from a technical standpoint is essential, it’s also crucial to consider
the end-users of the software - digital marketing teams. The CMS needs to have features that make it
straightforward for marketers to create, manage, and publish content across a variety of digital
channels. The CMS should enable business users to work e6ciently without technical knowledge or
coding experience. Content publishers should have complete cexibility to create customized content
that adheres to any/all branding options, move content and adjust page layouts for targeted device
types, audiences, languages, etc. - all without having to know a single line of code. Moreover, in a truly
hybrid CMS platform, the content publisher should be able to do these things in the CMS, or in any app
they create that communicates with the CMS via APIs.
At dotCMS, we’ve embraced this sentiment under our NoCode philosophy and provide a variety of
features like Edit Mode Anywhere and Advanced Workcows that are marketer-friendly.
Filed Under:
REPORT
DOWNLOAD
Recommended Reading
Pricing Community Careers Open Source Alternatives To Sharepoint: How to Choose an Enterprise-ready
Intranet Solution
30 Day Trial Videos News Room
Third-party Cookies and Personalization in dotCMS
Feature List Partners Contact Us
More Blogs