Hi All, According to the new C5 packaging structure, we are now planning to ship a single distribution for each product/solution containing a number of runtimes:
[image: Inline image 3] As I understood the main goals of this approach are reducing the size of the downloadable file (without duplicating common binaries in separate distributions) and making the tryout process much easier. Nevertheless, if we consider production deployments of such products/solutions, a typical deployment with HA may look as follows: [image: Inline image 4] As illustrated above, at the deployment time each runtime cluster would need a dedicated distribution (by removing unnecessary files), a set of configurations (may be using a configuration management module), a VM/container image, a VM/container orchestrator configuration (K8S replica-set, Marathon application, etc), etc. In this model, each runtime would map 1:1 to these entities. Most importantly, vendor signed runtime distributions might be needed for deployment verifications. Therefore, wouldn't it be better to ship runtime distributions together with the all-in-one distribution for each product/solution? If so people who wish to try-out products/solutions can use the all-in-one distribution and production deployments can use the other set. WDYT? - product/solution.zip - product-solution-runtime-1.zip - product-solution-runtime-2.zip - product-solution-runtime- n .zip T hanks Imesh -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh lean. enterprise. middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
