When to choose containers

Deploying Content Cortex containers instead of an on-premises installation can be preferable in a number of possible scenarios. But there are also reasons to maintain a standard on-premises installation model. Consider the relevant factors when deciding whether to use containers.

Deploying products in a container environment can be faster and easier than a standard on-premises installation. Additionally, updating software in a container environment can be simpler and less disruptive.

If you have the following requirements for your container environment, you might want to choose a container deployment:
  • Dynamic scalability to adjust to workload
  • Zero downtime support for patching
  • Ability to not only quickly patch or upgrade but quickly rollback to previous versions
  • Better resource usage and management
  • Better resiliency for your applications
If you have any of the following requirements, you might want to choose or maintain a standard on-premises installation:
  • Your platform and software choices are currently not supported by the container platform. For more information, see the Software and Product Compatibility Report External link opens a new window or tab.
  • You use custom applications that use the Content Platform Engine EJB protocol.
  • You use a single IBM Content Navigator instance to connect to IBM Content Manager in addition to IBM Content Cortex.
  • You use a single IBM Content Navigator instance to connect to Content Manager on Demand in addition to IBM Content Cortex.
  • You use Content Platform Engine Virtual Member Manager directory configuration.
  • You use the IBM Content Navigator Task Manager features, for example, Teamspace deletion or Box share.
  • For further information on limitations, see technote What are the current limitations for containerized deployments of Content Cortex and IBM Content Foundation External link opens a new window or tab.