Navigation

Executive Insight

Support for containerized deployment makes it easier for Independent Software Vendors (ISVs) to embed Alfresco Content Services into their applications or software-as-a-service, made possible via Alfresco’s OEM Program.

As described at the time of this major Alfresco product release, the main focus of Alfresco Content Services 6.0 was on significant architectural improvements, including a new containerized deployment option based on Docker and Kubernetes.  This is big news for developers who want to architect their application to take advantage of enterprise content management functionality in the form of microservices—breaking feature sets into component services that can be deployed independently.

oem-blog-digitization

Development & Deployment Advantages

Alfresco’s perspective is that containers can reduce inconsistencies and better support DevOps teams to accelerate development and deployment from the test environment through a staging system to production.  ISVs can deliver fast and standardized deployments across environments and reduce operational costs by being able to scale infrastructure up and down quickly depending on application workloads.

With the new Alfresco Content Services 6.0 release, it is now possible to deploy the product from a number of Docker images.  Docker images are now available for core parts of Alfresco Content Services like the “alfresco-content-repository,” “alfresco-search-services” or “alfresco-share,” as well as some supporting functionality such as image or document transformation.  Alfresco’s recommended approach 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 orchestrating Alfresco containers in a kubernetes cluster. It automates tasks like deployment, but also takes care of scaling and managing the containers in the cluster.

Enhancements to our REST API
In addition to adding support for containerized deployment, the Alfresco Content Services 6.0 release brings further enhancements to our REST API that benefit application developers from an integration point of view.  All the details regarding what is new with Alfresco Content Services 6.0 can be found in the documentation here.

Embed Alfresco Content Services 6.0 into your application or software-as-a-service
Alfresco has an OEM Program specifically designed to enable this and to ensure your success.  OEM licensing can be a superior alternative to building and supporting functionality in-house in terms of:

  1. Significantly reducing costs
  2. Accelerating time to market
  3. Increasing innovation

Check out my blog on the “build it or buy it?” topic here.  Likewise, you can hear directly from an Alfresco OEM partner, Pitney Bowes, on how they modernized their Commerce Cloud business by taking advantage of Alfresco technology.

Leave a comment

Previous Post:

© 2018 Alfresco Software, Inc. All Rights Reserved.