Hi All,

We are using  IBM App Connect Enterprise Version 11.0 in our project. We are running ACE in a docker containers which are running in kubernetes cluster in IBM cloud platform.

The size of initial ACE v11 base image which was provided was 1GB. After all the configurations and deployment of our applications in the image the image size became around 4GB. The size of the image continue of grow if we add new ACE v11 flows/app.

We are having two cluster and we are maintaining one ACE pod in each cluster.

Now the question comes on how to scale/manage these containers as these are not at all lightweight.

So there is a major problem we are facing on the scalability as every new pod we create it will consume 4GB.

Please note that we have a ACE v11 docker image with MQ installed in it and there is a need to use mq nodes.

I would like to hear suggestions from everyone on how to address this problem and is there any better way to handle/optimize this.

Appreciate help from all the experts.

Below is the ACE version information that we are using:

BIP8996I: Version: 11006
BIP8997I: Product: IBM App Connect Enterprise
BIP8999I: Build Type: Production, 64 bit, amd64_linux_2

BIP8974I: Component: DFDL-C, Build ID: 20190218-2330, Version: 1.1.2.0 (1.1.2.0), Platform: linux_x86 64-bit, Type: production


Regards,
Saha
IBM India



------------------------------
Prosanta Saha
------------------------------

Original Message:
Sent: 7/4/2020 12:24:00 PM
From: Prosanta Saha
Subject: Scalability of IBM ACEv11 docker containers

Hi All,

We are using  IBM App Connect Enterprise Version 11.0 in our project. We are running ACE in a docker containers which are running in kubernetes cluster in IBM cloud platform.

The size of initial ACE v11 base image which was provided was 1GB. After all the configurations and deployment of our applications in the image the image size became around 4GB. The size of the image continue of grow if we add new ACE v11 flows/app.

We are having two cluster and we are maintaining one ACE pod in each cluster.

Now the question comes on how to scale/manage these containers as these are not at all lightweight.

So there is a major problem we are facing on the scalability as every new pod we create it will consume 4GB.

Please note that we have a ACE v11 docker image with MQ installed in it and there is a need to use mq nodes.

I would like to hear suggestions from everyone on how to address this problem and is there any better way to handle/optimize this.

Appreciate help from all the experts.

Below is the ACE version information that we are using:

BIP8996I: Version: 11006
BIP8997I: Product: IBM App Connect Enterprise
BIP8999I: Build Type: Production, 64 bit, amd64_linux_2

BIP8974I: Component: DFDL-C, Build ID: 20190218-2330, Version: 1.1.2.0 (1.1.2.0), Platform: linux_x86 64-bit, Type: production


Regards,
Saha
IBM India



------------------------------
Prosanta Saha
------------------------------

Hi Saha, It is hard to know what to suggest given that 3GB of the size is down to your apps rather than the base image itself. Perhaps if you were to give us some more information about why your apps are consuming such a large size we could make recommendations? Also note that from ACEv11.0.0.7 you can define a remote default queue manager to use in containers which avoids the need of a local queue manager for most scenarios (including use of the Aggregation nodes, Collector, Sequence, Resequence and Timer nodes). The MQInput/Output/Get nodes of course already supported use of MQ Client connections much earlier from back in v10.  Cheers, Ben

------------------------------
Ben Thompson
IBM UK
------------------------------

Original Message:
Sent: Sat July 04, 2020 12:24 PM
From: Prosanta Saha
Subject: Scalability of IBM ACEv11 docker containers

Hi All,

We are using  IBM App Connect Enterprise Version 11.0 in our project. We are running ACE in a docker containers which are running in kubernetes cluster in IBM cloud platform.

The size of initial ACE v11 base image which was provided was 1GB. After all the configurations and deployment of our applications in the image the image size became around 4GB. The size of the image continue of grow if we add new ACE v11 flows/app.

We are having two cluster and we are maintaining one ACE pod in each cluster.

Now the question comes on how to scale/manage these containers as these are not at all lightweight.

So there is a major problem we are facing on the scalability as every new pod we create it will consume 4GB.

Please note that we have a ACE v11 docker image with MQ installed in it and there is a need to use mq nodes.

I would like to hear suggestions from everyone on how to address this problem and is there any better way to handle/optimize this.

Appreciate help from all the experts.

Below is the ACE version information that we are using:

BIP8996I: Version: 11006
BIP8997I: Product: IBM App Connect Enterprise
BIP8999I: Build Type: Production, 64 bit, amd64_linux_2

BIP8974I: Component: DFDL-C, Build ID: 20190218-2330, Version: 1.1.2.0 (1.1.2.0), Platform: linux_x86 64-bit, Type: production


Regards,
Saha
IBM India



------------------------------
Prosanta Saha
------------------------------