Below, we’ll explore the following aspects:<\/p>\n
- \n
- Supported stacks, along with details on clusterization specifics.<\/a><\/li>\n
- Management of auto-clustering.<\/a><\/li>\n
- Utilization of cloud scripting.<\/a><\/li>\n<\/ol>\n
Templates with Supported Auto-Clustering<\/h2>\n
At present, the clustering feature is supported by the following templates, with plans to incorporate additional stacks in the future:<\/p>\n
- \n
- Application servers:<\/strong> Tomcat\/TomEE<\/a>, GlassFish<\/a>, Payara<\/a>, Jenkins<\/a>, WildFly<\/a><\/li>\n
- SQL databases:<\/strong> MySQL<\/a>, MariaDB<\/a>, Percona<\/a>, PostgreSQL<\/a><\/li>\n
- NoSQL databases:<\/strong> Couchbase<\/a>, MongoDB<\/a>, Redis<\/a>, OpenSearch<\/a><\/li>\n
- Storage server:<\/strong> Shared Storage Container<\/a><\/li>\n<\/ul>\n
Tip:<\/strong> Your specific service hosting provider may offer the option to configure and implement auto-clustering for additional stacks not listed here.<\/div>\n<\/div>\nTomcat\/TomEE<\/h3>\n
A highly available Tomcat\/TomEE cluster is configured to distribute the workload across compute nodes, boosting performance and resilience. This setup includes session replication, context attribute replication, and cluster-wide deployment of WAR files.<\/p>\n
Note: The Auto-Clustering feature for Tomcat and TomEE is accessible from the following stack versions:<\/p>\n
Tomcat<\/a> – 10.0.5; 9.0.45; 8.5.64; 7.0.108<\/p>\n
TomEE – 9.0.0-M3; 8.0.5<\/p>\n
![\"Tomcat\/TomEE\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Tomcat-TomEE.png\" "\\"Tomcat\/TomEE\\"")
<\/a><\/p>\nGlassFish<\/h3>\n
The GlassFish<\/a> servers are set up to work together seamlessly, with session replication and load balancing already configured to optimize performance and reliability.<\/p>\n
![\"GlassFish\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/GlassFish.png\" "\\"GlassFish\\"")
<\/a><\/p>\nPayara<\/h3>\n
The Payara<\/a> servers are connected, with session replication and load balancing already configured to ensure smooth operation and optimize performance.
\n![\"Payara\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image25.png\" "\\"Payara\\"")
<\/a><\/p>\nJenkins<\/h3>\n
Within Jenkins<\/a>, there’s a master node operating in master-slave mode. It’s equipped with auto-scalable Java Engine workers and comes with pre-installed plugins. These plugins support automation for building and deploying, enabling the organization of continuous integration (CI) and continuous delivery (CD) pipelines.<\/p>\n
![\"Jenkins\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image15-1.png\" "\\"Jenkins\\"")
<\/a><\/p>\nWildFly<\/h3>\n
The WildFly nodes operate in Domain Mode with clustering enabled, ensuring high availability and continuous performance for deployed Java EE applications.<\/p>\n
![\"WildFly\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image8-3.png\" "\\"WildFly\\"")
<\/a><\/p>\nMySQL<\/h3>\n
Auto-Clustering is available for MySQL versions 5.7.x and 8.x exclusively.<\/p>\n
The automatic clusterization of databases includes pre-configured replication and auto-discovery of nodes.<\/p>\n
You have the option to choose from the following schemes<\/strong> based on your requirements:<\/p>\n
1. Primary-Primary<\/strong> with Extra Secondaries:<\/strong> This scheme features pre-configured replication with two interconnected primary databases. As the cluster scales horizontally, additional secondary nodes are seamlessly integrated.<\/p>\n
![\"MySQL](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image22.png\" "\\"MySQL")
<\/a><\/p>\n2. Primary-Secondary<\/strong> with Extra Secondaries scheme entails pre-configured replication with one primary and one secondary database. As the cluster scales horizontally, additional secondary nodes are seamlessly integrated.<\/p>\n
![\"MySQL](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image7-3.png\" "\\"MySQL")
<\/a><\/p>\nLearn more<\/strong>: https:\/\/github.com\/jelastic-jps\/mysql-cluster<\/a><\/p>\n
MariaDB<\/h3>\n
Auto-Clustering is exclusively available for MariaDB versions 10.x.<\/p>\n
The automatic clusterization of databases includes pre-configured replication and auto-discovery of nodes.<\/p>\n
You can choose from the following Scheme types based on your requirements:<\/p>\n
1. Primary-Primary<\/strong> with Extra Secondaries: This scheme features pre-configured replication with two interconnected primary databases. As the cluster scales horizontally, additional secondary nodes are seamlessly integrated.<\/p>\n
![\"MariaDB](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image21.png\" "\\"MariaDB")
<\/a><\/p>\n2. Primary-Secondary<\/strong> with Extra Secondaries: This scheme involves pre-configured replication with one primary and one secondary database. During horizontal scaling, the cluster expands with additional secondary nodes.<\/p>\n
![\"MariaDB](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image12-1.png\" "\\"MariaDB")
<\/a><\/p>\n3. Galera Cluster:<\/strong> In this setup, all servers can accept updates concurrently, even if issued simultaneously.<\/p>\n
![\"Galera](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image27.png\" "\\"Galera")
<\/a><\/p>\nPercona<\/h3>\n
The automatic clusterization of databases includes pre-configured replication and auto-discovery of nodes.<\/p>\n
Based on your requirements, you have the option to select from the following scheme types:<\/p>\n
1. Primary-Primary<\/strong> with Extra Secondaries: This scheme entails pre-configured replication with two interconnected primary databases. As the cluster scales horizontally, additional secondary nodes are seamlessly integrated.<\/p>\n
![\"Percona](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image3-4.png\")
<\/a><\/p>\n2. Primary-Secondary<\/strong> with Additional Secondaries: This configuration involves pre-configured replication with one primary and one secondary database. As the cluster expands horizontally, additional secondary nodes are seamlessly incorporated.<\/p>\n
![\"Percona](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image6-3.png\" "\\"Percona")
<\/a><\/p>\nMoreover, you have the option to utilize the XtraDB Cluster<\/strong>, a robust database clustering solution designed to ensure high availability, mitigate risks of downtime and data loss, and provide linear scalability to support a growing environment.<\/p>\n
![\"XtraDB](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image5-3.png\" "\\"XtraDB")
<\/a><\/p>\nPostgreSQL<\/h3>\n
A pre-configured PostgreSQL database cluster is established with asynchronous primary-secondary replication, allowing for the automatic addition of new nodes into the cluster as secondaries.<\/p>\n
![\"PostgreSQL\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image9-2.png\" "\\"PostgreSQL\\"")
<\/a><\/p>\nCouchbase<\/h3>\n
The Couchbase servers are automatically interconnected with pre-configured auto-scaling and rebalancing, ensuring a unified, highly available data storage system.<\/p>\n
![\"Couchbase\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image24.png\" "\\"Couchbase\\"")
<\/a><\/p>\nLearn more:<\/strong> https:\/\/github.com\/jelastic-jps\/couchbase<\/a><\/p>\n
MongoDB<\/h3>\n
Automatically configure a highly-available and reliable MongoDB replica set, complete with auto-discovery of new nodes for seamless integration.<\/p>\n
![\"MongoDB\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image16-1.png\" "\\"MongoDB\\"")
<\/a><\/p>\nRedis<\/h3>\n
Automatization is provided for the distributed implementation of a Redis Cluster, an open-source, in-memory data structure store. Typically used for caching, data storage, acting as a message broker, and various other tasks. The topology includes a minimum of three Primary servers, each accompanied by a Secondary node to facilitate read load distribution and auto-recovery in case of Primary server failure.<\/p>\n
![\"Redis\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image13-1.png\" "\\"Redis\\"")
<\/a><\/p>\nOpenSearch<\/h3>\n
Automatic clustering of a community-driven, open-source search engine that offers distributed, multitenant full-text search. The solution has built-in options for integrating OpenSearch Dashboards for data visualization and Logstash for log processing.<\/p>\n
![\"OpenSearch\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image4-4.png\" "\\"OpenSearch\\"")
<\/a><\/p>\nShared Storage Container<\/h3>\n
The AccuWeb.Cloud platform automatically configures a dependable storage cluster using the Gluster<\/a> solution, guaranteeing data safety. In the event of node failure, the AutoFS client seamlessly switches to operational instances, ensuring high availability of storage resources.<\/p>\n
![\"Shared](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image23.png\" "\\"Shared")
<\/a><\/p>\n<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nAuto-Clustering Management<\/h2>\n
1.<\/strong> The Auto-Clustering feature can be activated for the node group using the corresponding switcher located in the central part of the topology wizard, provided it is available for the selected stack.<\/p>\n
![\"Auto-Clustering](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image2-4.png\" "\\"Auto-Clustering")
<\/a><\/p>\nTip:<\/strong> Depending on the specific implementation, the Auto-Clustering<\/strong> option may vary:
\nI.<\/strong> It could be mandatory, requiring automatic activation (e.g., for the Couchbase database).![\"Auto-Clustering](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image18.png\" "\\"Auto-Clustering")
<\/a><\/p>\nII.<\/strong> It may be mandatory with additional settings available (e.g., cluster scheme and ProxySQL load balancer for the MySQL database).<\/p>\n
![\"Cluster](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image20.png\" "\\"Cluster")
<\/a><\/p>\nIII.<\/strong> It might come with restrictions, such as minimum\/maximum node counts or scaling modes (e.g., for the MariaDB Galera type).<\/p>\n
![\"Node](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image1-5.png\" "\\"Node")
<\/a><\/p>\n<\/div>\n<\/div>\n2.<\/strong> Additionally, to obtain further details about the cluster being created, hover over the question mark icon adjacent to the switcher. In the resulting pop-up frame, you’ll find a brief description, often accompanied by a topology scheme and a link to a more comprehensive overview.<\/p>\n
![\"Question](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image11-1.png\" "\\"Question")
<\/a><\/p>\nFor details on different database cluster types, click on the corresponding “Scheme<\/strong>“:
\n![\"Scheme\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image10-1.png\" "\\"Scheme\\"")
<\/a><\/div>\n<\/div>\n3.<\/strong> Other settings can be configured similarly to any regular environment.<\/p>\n
- SQL databases:<\/strong> MySQL<\/a>, MariaDB<\/a>, Percona<\/a>, PostgreSQL<\/a><\/li>\n
- Management of auto-clustering.<\/a><\/li>\n
![\"Configure\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image19.png\" "\\"Configure\\"")
<\/a><\/p>\n![\"Platform](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/image17-1.png\" "\\"Platform")
<\/a><\/p>\n