Blog

Should You Standardize on a Single CMS?

There’s too little conversation about standardization regarding content management systems (CMS), and too much business value lost in not considering it. We’ve written an eBook discussing the topic, but how do you know if standardizing is right for you?

The key to success with any web project – from app design to a new site build to adding interactive functionality – starts with intention. To create a more purposeful web, it’s important to challenge clients who know what they want but not what they need.

With any project – big or small, rescue or new – we start our process with a Discovery.

The Discovery process is simple – it’s an open, straightforward conversation that uncovers two important pieces of information:

No one wants to be the person who invested hundreds of thousands of their company’s dollars into a new website, app or digital asset, and then have it fail to do what it was built to do.

Even fewer people want to be the ones to then tell their management team that the project needs even more investment – sometimes as much as the initial expenditure – to fix the problems; or worse, start over.

In the web industry, we call this a rescue. They are every bit as horrible as they sound, but there’s good news. They can be prevented.

Elasticsearch will take any data you throw at it, but without a predefined index, it will try to figure out the data type on its own, which can result in both inefficient storage and querying. It can also limit ways to use your data in some cases.

Let's consider http status codes for example. These values are always integers, however Elasticsearch will treat them like text unless you explicitly define your index.

We started offloading web logs from Acquia into Elasticsearch, and let me tell you, it's been amazing!

Imagine being able to query your apache access log for https status 500 errors that occurred in the last 4 hours; or retrieving the most common 404 paths. Maybe you're more visual and want to see pie charts of bytes downloaded per country, or histograms of status codes per half hour. Perhaps you want to trace the footprints a certain IP address made on a particular domain, then across multiple domains.