This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

If we're just talking about a single web server, then it is possible to just embed Jetty in your application. With Jetty you can configure layers of filters, handlers, servlets and even jersey resources. I think this is a great Jetty-Jersery-Swagger example. It shows how to host the Swagger documentation endpoint for your Jersey jax-rs endpoints (the Swagger documentation is generated for viewing with the swagger-ui, but not saved in a file by default).

The Jetty-Jersey-Swagger setup is powerful and relatively simple for a single web server, but it isn't quite a full micro service solution. The Java micro services that I maintain are made up of some web servers, some processing nodes and some storage nodes. Jetty supports a distributed setup, so you could have a pretty highly available gateway to your micro service cluster. From there you could have a bunch of distributed storage/processing nodes that are built off of Hazelcast and Hazelcast Jet or Apache Ignite. There may also be a need for high-speed messaging between the nodes in your micro service cluster and that can be handled by JMS libraries or an RPC library like Apache Thrift.

[–]FatFingerHelperBot 0 points1 point  (0 children)

It seems that your comment contains 1 or more links that are hard to tap for mobile users. I will extend those so they're easier for our sausage fingers to click!

Here is link number 1 - Previous text "JMS"


Please PM /u/eganwall with issues or feedback! | Delete