Well one of your responses indicated that the the blogpost suggests
wrapping all DB calls in circuit breakers, and Frank's response indicated
that it is suggesting wrapping all calls to external systems in circuit
breakers. If it can confuse such brilliant minds, I guess it could mislead
an averag
Azeez, asking questions and asking to understand what the purpose of some
code is not a criticism.
Of course there should be a sample! I only asked about it because to me a
client side sample made more sense - and then it went into a discussion of
when this should be used etc..
I would not only p
Hi Samitha,
Great . There are few suggestions. It is good if we have the functionality
of updating the process variables configuration from PC to DAS and PC to
BPS. Process artifacts will be changed time to time and variables will be
changed. And also generated spark scripts should be customizable
Hi Eranga,
Squashing the image is a problematic approach for WSO2 products, as some
configs that are done in the entrypoint script would also get saved in to
the resulting flat image. For example, there are some operations that take
the IP address of the container as an input. If we flatten the co
+1 to this idea in general.
Before this change, the Dockerfiles had the puppet apply command hardcoded.
A user did not need a puppet installation in the local machine since the
Dockerfile commands are run in a temp container. But still the puppet
related complexities (puppet related directory stru
Hi,
To reduce the size of the docker image I found the following approaches
being used. Once the image if built we can merge the layers and flatten
[1]. Also can squash the docker image as in [2]
[1] https://www.ctl.io/developers/blog/post/optimizing-docker-images/
[2] https://github.com/jwilder/
