Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/juanavelez/vertx-dependent-verticle-deployer
A Vert.x Verticle intended to deploy verticles and their dependent verticles
https://github.com/juanavelez/vertx-dependent-verticle-deployer
reactive vertx
Last synced: about 2 months ago
JSON representation
A Vert.x Verticle intended to deploy verticles and their dependent verticles
- Host: GitHub
- URL: https://github.com/juanavelez/vertx-dependent-verticle-deployer
- Owner: juanavelez
- License: apache-2.0
- Created: 2017-01-28T19:11:29.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2019-01-11T02:47:31.000Z (almost 6 years ago)
- Last Synced: 2024-08-04T01:09:16.713Z (5 months ago)
- Topics: reactive, vertx
- Language: Java
- Homepage:
- Size: 28.3 KB
- Stars: 6
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- vertx-awesome - Vert.x Dependent Verticle Deployer - A Vert.x Verticle intended to deploy verticles and their dependent verticles. (Utilities)
README
# Vert.x Dependent Verticle Deployer
[](https://travis-ci.org/juanavelez/vertx-dependent-verticle-deployer)
[](https://search.maven.org/#search%7Cga%7C1%7Ccom.chibchasoft.vertx-dependent-verticle-deployer)
[](https://codecov.io/gh/juanavelez/vertx-dependent-verticle-deployer)
An implementation of a Vert.x verticle that deploys other verticles and their dependents. This is useful when coordination is needed between several verticles, for example a verticle that serves pages which are populated by another verticle that depends on external resources cannot start until the external resources verticle has successfully started.
## Components
The main driver of deployment is the DependentVerticleDeployer verticle.
### DependentVerticleDeployer
The DependentVerticleDeployer verticle is the main entry point and as such all it does is deploy one or more verticles and their dependents. Those verticles and their dependents may have their own `DeploymentOptions`. The information on what verticles to deploy, their dependents and DeploymentOptions are all encapsulated in a `DependentsDeployment` object.
The DependentVerticleDeployer completes sucessfully its startFuture (`AbstractVerticle::start(Future startFuture`) only when all verticles (and their dependents and so on) have been successfully deployed. If any verticle fails to deploy, the startFuture is failed. Since the deployment of verticles is done "in parallel" (via `Vertx.deployVerticle(String, Handler)` or `Vertx.deployVerticle(String, DeploymentOptions, Handler)`), it is possible that even though the startFuture has failed, other verticle deployments could still be executing.
**NOTE:** It is strongly suggested that the DependentVerticleDeployer be deployed as a single instance. The DependentVerticleDeployer is not to be intended to be deployed as multiple instances and its behaviour is not guaranteed if such action is taken. This is not to say that verticles in `DependentsDeployment` cannot be deployed as multiple instances (via `DeploymentOptions.setInstances`).
### DependentsDeployment and DeploymentConfiguration
The `DependentsDeployment` is an object encapsulating one or more `DeploymentConfiguration` objects (`List getConfigurations()`).
The `DeploymentConfiguration` itself is an encapsulation of the name of the verticle (including any prefixes) to deploy (`String getName(), setName(String)`), any deployment options for such verticle (`DeploymentOptions getDeploymentOptions(), setDeploymentOptions(DeploymentOptions)`) and the list of (any) dependents to deploy (`List getDependents()`).
Each `DeploymentConfiguration` object also includes the DeploymentID assigned by Vertx upon successful deployment (`String getDeploymentID()`) as well as methods to indicate completion, success, failure and cause of failure (`boolean isComplete(), boolean sucess(), boolean failed(), Throwable failCause()`).
Both `DependentsDeployment` and `DeploymentConfiguration` provide a way to create such objects from a `JsonObject` (`DependentsDeployment::fromJson` and `DeploymentConfiguration::fromJson`) as well as to obtain `JsonObject`s from themselves (`DependentsDeployment::toJson` and `DeploymentConfiguration::toJson`).
## Usage ##
Vert.x Dependent Verticle Deployer is published to the [maven public repo](http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.chibchasoft%22%20AND%20a%3A%22vertx-dependent-verticle-deployer%22).
Add the vertx-dependent-verticle-deployer dependency to your project, in case of maven like this:
```xml
com.chibchasoft
vertx-dependent-verticle-deployer
1.0.2-SNAPSHOT
```
where VERSION is [](https://search.maven.org/#search%7Cga%7C1%7Ccom.chibchasoft.vertx-dependent-verticle-deployer)
Configure the verticles to deploy (and their dependents) using both `DependentsDeployment` and `DeploymentConfiguration`:
```java
// "TheDependentVerticle" needs to be deployed only if "InitialVerticle" is deployed successfully.
DeploymentConfiguration dependentVerticleCfg = new DeploymentConfiguration();
dependentVerticleCfg.setName("TheDependentVerticle");
dependentVerticleCfg.setDeploymentOptions(new DeploymentOptions().setWorker(true).setInstances(2));
DependentsDeployment innerDepDeployment = new DependentsDeployment();
innerDepDeployment.getConfigurations().add(dependentVerticleCfg);
// When "InitialVerticle" succeds its deployment, "TheDependentVerticle" needs to be deployed.
DeploymentConfiguration initialVerticleCfg = new DeploymentConfiguration();
initialVerticleCfg.setName("InitialVerticle");
// Add "TheDependentVerticle" DependentsDeployment as a dependent of "InitialVerticle"
initialVerticleCfg.getDependents().add(innerDepDeployment);
// The "OtherVerticle" has no dependents and can be deployed at the same time as the "InitialVerticle"
DeploymentConfiguration otherVerticleCfg = new DeploymentConfiguration();
otherVerticleCfg.setName("OtherVerticle");
initialVerticleCfg.getDependents().add(innerDepDeployment);
DependentsDeployment dependentsDeployment = new DependentsDeployment();
dependentsDeployment.getConfigurations().add(initialVerticleCfg);
dependentsDeployment.getConfigurations().add(otherVerticleCfg);
```
Create a new `DependentVerticleDeployer` instance and set its `depedentsDeployment ` property using the previoulsy configured `DependentsDeployment` object and deploy it:
```java
DependentVerticleDeployer dependentVerticle = new DependentVerticleDeployer();
dependentVerticle.setDependentsDeployment(dependentsDeployment);
Vertx.vertx().deployVerticle(dependentVerticle, ar -> {
if (ar.failed()) {
LOG.warn("Failed to deploy " + dependentsDeployment.toJson().encode(), ar.cause());
} else {
LOG.info("InitialVerticle DeploymentID=" + initialVerticleCfg.getDeploymentID());
LOG.info("OtherVerticle DeploymentID=" + otherVerticleCfg.getDeploymentID());
LOG.info("TheDependentVerticle DeploymentID=" + dependentVerticleCfg.getDeploymentID());
}
});
```