From the point of view of DevOps, a key concept behind the micro-service architecture that can quickly deploy multiple instances of micro services to respond to changing application environments (such as a sudden influx of user requests, the internal problems of infrastructure, etc.).
To achieve this, the micro-service needs with all dependencies as a single package and product installation, then this product can be deployed on any server Java JDK installed. These dependencies further includes a micro bearer service runtime engine (such as an HTTP server or application container).
This continuous build, packaging and deployment process is the service assembly (FIG step 2-61). Figure 2-7 shows additional details about the services of assembly steps.
.jpg)
Fortunately, almost all of Java Micro Services Framework contains runtime engine can use the code to package and deploy. For example, in the example of FIG Spring Boot 2-7 may be used to build a Maven and Spring Boot executable Java JAR file having embedded Tomcat engine built therein. The following command-line example will serve as a permit to build an executable JAR, and then start the JAR file from the command line:
-
mvn clean package && java ¨Cjar target/licensing-service-0.0.1-SNAPSHOT.jar
For some operation and maintenance team, will embed the concept of environmental runtime JAR file is a major shift in the deployment of their applications. In traditional J2EE enterprise organizations, the application is deployed to the application server. This model means that the application server itself is an entity and is usually managed by a team of system administrators, those administrators to configure the management server, regardless of the application is deployed.
During deployment, the configuration of the separation between the application server and the application may be introduced into the point of failure, because in many tissues, configuring an application server is not the source control, and by a combination of user interfaces and local manner management script management. This configuration is very prone to drift in the application server environment, resulting in a sudden and seemingly random circumstances is interrupted.
The runtime engine embedded products can be deployed in practice eliminates the possibility of a number of configuration drift. It also allows the entire product placed under source control, and allows application teams to better consider how their applications are built and deployed.