Hi, Given several issues we discovered with automatic artifact synchronization with DepSync in C4, we have discussed how to approach this problem in C5.
We are thinking of not doing the automated artifact synchronization in C5. Rather, users should use their own mechanism to synchronize the artifacts across a cluster. Common approaches are RSync as a cron job and shell scripts. But, it is vital to know the artifact deployment status of the nodes in the entire cluster from a central place. For that, we are providing this deployment coordination feature. There will be two ways to use this. 1. JMS based publishing - the deployment status will be published by each node to a jms topic/queue 2. Log based publishing - publish the logs by using a syslog appender [1] or our own custom appender to a central location. The log publishing may not be limited to just the deployment coordination. In a containerized deployment, the carbon products will run in disposable containers. But sometimes, the logs need to be backed up for later reference. This will help with that. Any thoughts on this matter? [1] https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender Thanks, KasunG -- ~~--~~ Sending this mail via my phone. Do excuse any typo or short replies
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
