Shulou(Shulou.com)06/01 Report--

What are the 13 most popular Java micro-service frameworks? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

There used to be many different chip architectures and operating systems in the server field. after long-term development, Java's "compile once, run everywhere" made it find a place in the server field and become a favorite of programmers.

We will share with you 13 reliable Java microservice architectures.

1 、 Spring Boot

Java has been building Spring applications for a long time, and Spring Boot is a specific version of Spring that makes it easier to build microservices by handling configuration details. Spring Boot is created to self-launch any type of Spring project, not just a microservice. When the application is complete, Spring Boot will be mixed in the web server and output a JAR file, except for JVM. You can think of it as the original Docker container. This is why many developers responsible for building microservices like Spring Boot very much.

Using Spring to develop micro services follows the same MVC philosophy as Web applications. The framework enjoys all the deep connections established over the years of Java development, including the integration of all primary and secondary data stores, LDAP servers, and messaging tools such as Apache Kafka. There are also many small features for maintaining a collection of running servers, such as Spring Vault, a tool for maintaining the passwords required by servers in a production environment. All of these advantages explain why Java programmers have loved Spring Boot for many years.

2 、 Eclipse MicroProfile

In 2016, the Java Enterprise community decided to clean up the content in Java Enterprise Edition so that people could use classic widgets to build simple microservices. They removed a large number of libraries, but retained the functional code that handles REST requests, parses JSON, and manages dependency injection, which is eventually called Eclipse MicroProfile, which is fast and simple.

Since then, the MicroProfile community has developed an agreement to release a new version every quarter, while adding new code to keep the microservice running smoothly and safely. Any Java EE developer will be very familiar with the development process and code structure, but also to save the configuration hassle.

3 、 Dropwizard

When Dropwizard appeared in 2011, the Dropwizard framework provides a very simple model for developers, which contains many important modules. You can add some business logic or configure other content according to your needs. In the end, you will find that the JAR file is very small and can be started quickly.

Perhaps the biggest limitation of Dropwizard is the lack of dependency injection. If you want to use dependency injection to keep your code clean and loosely coupled, you need to add your own libraries, unlike Spring, but now Dropwizard also supports most features, including logging, health checking, and providing flexible code.

4 、 WildFly Thorntail

The Red Hat staff built their own version of MicroProfile using a flexible configuration tool. The framework was originally called WildFly Swarm, but was later renamed WildFly Thorntail,Thorntail to help you create your own Maven build file by specifying the features you need, and then Maven is responsible for assembling everything.

Thorntail will also scan the code to detect components, or it can be overwritten with a BOM (bill of materials) file. When it's all running, Thorntail removes the unused parts of Java Enterprise Edition and creates a small JAR file that can be deployed with one command-- a clever feature that allows Thorntail projects to call it Uber-JAR. This is another traditional way to follow Java Enterprise Edition, which does not retain all the heavy burden.

5 、 Helidon

Helidon removes Java Enterprise Edition, retains a lightweight, servlet-based core, and attracts a large number of fans. In Helidon, developers from Netty, and add code for routing and error handling. It uses two basic models of the code, the so-called SE and MP versions.

Node developers may be more familiar with Helidon SE because it has function calls connected by periods. Java programmers who use JAX-RS are more familiar with Helidon MP. In addition, Helidon integrates some well-received tools, which are the reasons why it attracts a large number of developers.

6 、 Cricket

Another one for rapid API development frameworks is Cricket. Cricket is small, although it includes many additional features, such as key data storage, to avoid connecting to databases and schedulers to control background repetitive processing. No complexity or other dependencies are added, so it's easy to add code to Cricket and start stand-alone microservices.

7 、 Jersey

One of the standard ways to develop web services is the Java API (aka JAX-RS) of RESTful web services, which is a general specification implemented in the Jersey framework. This approach relies primarily on the use of annotations to specify path mapping and return details. Everything else from parameter parsing to JSON packaging is handled by Jersey.

The main advantage of Jersey is that it implements the JAX-RS standard, which is so popular that some developers are used to combining Jersey with Spring Boot.

8 、 Play

One of the best ways to experience JVM's cross-language capabilities is to use the Play framework, which is compatible with Java or any other JVM language. Its foundation is very modern, with an asynchronous, stateless model that does not overload the server by threads trying to track users and their session data. There are many additional features that can be used to enrich the site, such as OpenID, validation, and file upload support.

The Play code base has been developed for more than a decade, so you'll also find ancient features similar to support for XML. Play is mature and light, and this combination is quite distinctive.

9 、 Swagger

Building an API looks as simple as writing code that listens to a port, but Swagger developers don't think so. They have created a complete API specification language, OpenAPI, which you can use to illustrate your API. This seems like an extra step, but the Swagger team also provides code to transform the specification into automated tests, documentation, and so on.

The API in the Swagger configuration file is simple and is used to implement the interface, document the interface, and provide a set of tools to test the code built under it, and even an API governance mechanism.

Swagger is an api ecosystem, which is not limited to Java. If your team migrates to Node.js or any of dozens of other languages, there is a Swagger Codegen module that translates the OpenAPI specification into an implementation of that language.

10 、 Restlet

One of the biggest differences between different frameworks is the number of connections to other services or libraries. The Restlet project, which provides a larger set of features and connections, has integrated with libraries such as JavaMail, avoiding the need for microservices to use POP, IMAP, or SMTP; on some mail servers to prevent building large text indexes and metadata, as well as integrating Lucene and Solr.

There are still many features in Restlet that are under development. For example, you don't need to use JSON because it works directly with XML, CSV, YAML, and other file formats, and it allows users to test api from Chrome browsers.

11 、 Squash

Debugging microservices has always been a challenge for developers because these components are loosely coupled and it is difficult to track data flow through all layers of the system. By using Squash, you can set breakpoints in the code running on the Kubernetes cluster and then receive all the data in the IDE as if you were running the code locally. Squash also integrates Node.js and Python runtime

12 、 Telepresence

Another option for debugging is to use Telepresence, which creates local proxies for microservices on remote Kubernetes clusters. In the local version, you can set breakpoints or perform any action that can be done on the local computer.

13 、 Zipkin

Zipkin is used to record events on various microservices, allows developers to collect monitoring data on various Twitter services, and provides query interfaces. Zipkin has at least six language implementations, such as Java, so it can handle multilingual systems. Many frameworks have integrated Zipkin in some form, such as Spring.

After reading the above, have you mastered the methods of each of the 13 most popular Java microservice frameworks? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.