The Microservices architecture emerged as a result of overall advances in software architecture and the build process. With Microservices, the responsibility for solving the problem domain is no longer delegated to a single monolithic system with many functionalities.
A Microservice is bound to a specific context in the problem domain. As a purely architectural approach, building a Microservice does not imply any way of assembling the application, building it, or running it. There are no technical implications whatsoever. In order to build a Microservice, the problem domain must be analyzed, then a set of mutually exclusive services is shaped and developed. It can be programmed in the same language as a monolith, built in the same way as a monolith and, of course, run in the very same manner. The Microservices internal architecture may be arbitrary, and the same architectural principles for building monoliths may be leveraged when building Microservices.
However, Microservices and the way applications are built nowadays allow strong paradigm shifts.The aim of this chapter is to provide the reader with a thorough understanding of the various possibilities of the Java Microservices shipment. The reader is able to recognize attributes of different ways of packaging Java applications. The goal of this chapter is to teach the reader to be able to evaluate the benefits and disadvantages of each and every Java application distribution model. Therefore, we will look at how packaging affects the process of the Microservice development, packaging, and distribution.
The following topics will be covered in this chapter:
- Introduction to Java Packaging
- Java EE MicroService Solution
- Deployment Architecture for Microservices