Workspace Lifecycle Management - padogrid/padogrid GitHub Wiki
◀️ Software List :link: Creating RWE ▶️
The cluster lifecycle management commands work for all the supported data grid products. Prior to PadoGrid 0.9.6, you could only manage a single product per workspace. Starting PadoGrid 0.9.6, this limitation has been lifted so that you can create and manage any number of heterogenous products in a single workspace. With this support, for example, you can create Hazelcast, Spark, Kafka, and Hadoop clusters in a workspace and start and stop all of them with the start_workspace and stop_workspace commands (see Managing Workspaces). Furthermore, you can group select clusters within a workspace and manage them as a whole using the start_group and stop_group commands (see Understanding Groups). You can also always start and stop each cluster individually by running the start_cluster and stop_cluster command.
Working with multiple products in a single host gives you the flexibility and simplicity of using local resources which translates to attaining optimal performance compared to Docker or Kubernetes, but it does come with a price. You must carefully select unique port numbers to prevent conflicts between products. With PadoGrid, however, the port conflict issue is easily handled by simply specifying the start port number using the create_cluster -port option. PadoGrid will automatically increment all the port numbers of the cluster using the difference between the start port number and the default port number as the increment factor.
The default ports for each product are documented in the following link with create_cluster -port examples.
◀️ Software List :link: Creating RWE ▶️