The new Alfresco Content Services 6.0 is released, and I am happy to share the highlights of this version with you.
The major focus of the new Alfresco Content Services 6.0 release was on significant architectural improvements, including a new containerized deployment option based on Docker and Kubernetes.
For those customers that have not yet begun to take advantage of containers and prefer a more traditional way of installing Alfresco Content Services, we continue to deliver the .WAR files for manual deployment. But for now, let’s focus on the new containerized deployment with Docker and Kubernetes.
As customers embrace DevOps, infrastructure as code, the cloud, and Alfresco, the capabilities introduced in Alfresco Content Services 6.0 deliver a step change in time-to-value.
What’s in for customers?
- Accelerates development and deployment – containers reduce environment inconsistencies and support DevOps to accelerate development and deployment from the test environment through a staging system to production
- Uses trusted Open Source industry technologies – based on Docker & Kubernetes, customers can deliver fast and standardized deployments across environments
- Reduces operational cost – customers are now able to scale the infrastructure up and down quickly depending on the current workload.
Want to give it a try?
You can test the new improvements around Docker and Kubernetes and start a 30 day free trial.
Current Alfresco images
The screenshot below shows the currently available Alfresco Docker images that provide:
- Core parts of Alfresco Content Services like the “alfresco-content-repository,” “alfresco-search-services” or “alfresco-share”
- Some supporting functionality, such as for image or document transformation
How to get started with Docker and Kubernetes
With the new Alfresco Content Services 6.0 release, it’s now possible to deploy the product from a number of Docker images as described above. But it would be a time-consuming and complex task to deploy individual Docker containers based on these images as, you’d have to do the configuration to make them work together.
Therefore, the recommended way is to use a Docker-compose file to get to a “one-click to deploy” experience. A Docker-compose file describes the containers of the environment and starts those containers. We provide further information and an example of a Docker-compose file on the official documentation site at https://docs.alfresco.com/6.0/tasks/deploy-docker-compose.html
For production environments, we recommend to orchestrate our containers in a kubernetes cluster. It automates tasks like deployment, but also takes care of scaling and managing the containers in the cluster.
What else is included in the new release?
- Library upgrades to ensure ongoing security and to have the ability to leverage more capabilities in future releases
- Further improvements around our REST API
Where to get further information?