User Answers

Hi Robert,

I can confirm that we do not plan to port container improvements to Caché or Ensemble. Our Focus is IRIS only.

Ccontainermain is the way to go for your case.



Hi Dmitry,

It looks like they put up with us :-) for about a year (see reported issues)

We are addressing this. Stay tuned and thanks for your prompt alerting.

In general, it is a good thing to have these 2 concerns (code vs data) separate. You're de-coupling 2 items (concerns, concepts) that are effectively different. When using technologies like containers & container services this point becomes even more apparent and allow you to be much more flexible and agile in your deployments. Of course, schema migration is still an issue, but the separation still helps. This is one of the reason why orgnaizations can perform multiple deployments per day.


Use the official and documented API.

If pure existence or simply the class is defined (but not compiled)

SAMPLES>w ##class(%Dictionary.ClassDefinition).%Exists($lb("Aviation.Aircraft"))

If you're after existing and compiled:

SAMPLES>w ##class(%Dictionary.CompiledClass).%Exists($lb("Aviation.Aircraft"))




Are you using the ccontainermain from the github account as pointed out by @Dmitry? Or do you have your own solution?


Hi John,

InterSystems has shifted gear into a more agile, cloud-oriented approach that is going to leverage & be better integrated with a DevOps modus operandi.

InterSystems will unveil such new approach and what goes with it at this year Global Summit in September.


one way to configure your system is to edit the cache.cpf file


Ha... there was another question on MS-Windows support :)

Given the Docker engine dependency on the Linux Kernel, the dependencies or support of the various Linux FS and that the September announcement was just for a GA version on Win server 2016, I would not waste my time right now.

Spin up a Linux node on your private or public cloud and just enjoy the speed and lightness of containers. :)


Thanks @Dmitry; perfect.

@Andrew: as you can appreciate Docker containers can be very suitable for just about any use case when you want to embrace infrastructure-as-code and, even better, immutable infrastructure. Of course, we are already talking about automation, provisioning, deployment process and, in many cases, DevOps and why-not? Microservices.

FWIW this is a huge chapter and we are not even mentioning global mapping or SLM (subscript level mapping), how dynamic you might want to be with it and what kind of elasticity you are after (scaling out and back in). You might find that ECP is not really your friend right here and right now given your cloud-based requirements. ECP is however extremely good for what it was created to do.