This article focuses on the Static CMS Hybrid-Headless architectural pattern and how it can have significant advantages against its similar, but not identical, traditional or monolithic Hybrid-Headless counterpart.
In this article, we'll discuss how many CMS vendors have extended their existing platforms to provide two (or more) of the fundamental architectures in an attempt to win the battle to the top.
In this article, we'll discuss the most common types of publishing architectures within the world's content management system (CMS) platforms from a business owner's perspective. We'll explain what each is and highlight the various advantages of each, but we'll also highlight some things to be aware of when you select a particular platform architecture.
At Crownpeak, we built SDKs for the three main SPA frameworks (React, Vue.JS and Angular) to seamlessly "wire up" the SPA to data provided by DXM and to generate all of the DXM configuration required to support the authoring capabilities. The ability to iterate through an application, identify everything required to support the content author, and automatically generate it all (i.e., templates, components, models) saves days of work!
Crownpeak Digital Experience Management (DXM)’s Decoupled Content Deployment Architecture provides organisations with complete flexibility in what, how and where content is distributed. In today’s modern customer-experience-focussed world, the ability to curate content in a single location, taking advantage of centralised governance while enabling local market flexibility, then deploying this optimised content to the right channel for the customer at the right time, gives global organisations a strategic advantage over their competitors.
This post describes installation & configuration of a single node installation, built on-top of CentOS6. It assumes that internet access is available from the OS.
This post describes installation & configuration of a basic 2-node cluster built on-top of CentOS 6. It assumes that internet access is available from the OS.
This post describes installation & configuration of a basic 2-node cluster built on-top of CentOS 6. It assumes that internet access is available from the OS.
This post describes how to configure CentOS for load balancing via LVS (http://www.linuxvirtualserver.org/) and Piranha (https://www.redhat.com/software/rha/cluster/piranha/). It is by no means a debugging guide, but explains the basics.
I'm going to install the Grid Hub system upon a standard CentOS 6 installation, and then connect it to multiple remote instances, running across a variety of Windows operating systems.
Recently I've needed to request a new SSL certificate for a website running on IIS6. The existing website has a certificate that I'm looking to replace, but as this was originally generated as a 1024-bit certificate, I cannot prepare a new request for the website through the IIS6 tools - I can only renew it.
I'm working on some C# project components that I need to run under CentOS6. Mono (http://www.mono-project.com) is an open source implementation of Microsoft's .NET Framework based on the ECMA standards for C# and the Common Language Runtime. With Mono installed, many of the .NET features will be available under the CentOS platform.
Siege is an http load testing and benchmarking utility. It was designed to let web developers measure their code under duress, to see how it will stand up to load on the internet.