Payara Micro allows you to run web applications in a self-contained and easy way. Since the release of the Payara Server in May 2016, there is a simple way to generate an "Uber" JAR that bundles the contents of a WAR file and the classes and resources that compose Payara Micro!

Note that this "Uber" Jar is not the best way to run your application in a Docker container as it requires an update of the entire binary for each small code change you make in the application. A better solution is just to start a Payara Micro Instance and point to the application that needs to be installed. More information can be found on our Payara Micro Docker Image documentation.

(last updated 06/04/2021)

The HealthCheck Service provides automatic self-monitoring in order to detect future problems as soon as possible. The HealthCheck Service was introduced in Payara Server and Payara Micro version 161 and some new metrics have been added in version 162.

All the functionality of the HealthCheck Service that is available in Payara Server is also included in Payara Micro. However, as Payara Micro differs in some concepts from Payara Server, the usage and configuration of the HealthCheck Service is slightly different. In this post, we will focus on how to use it in Payara Micro.

 

Payara Micro 162   can now deploy your artifacts stored in Maven repositories simply by providing the GAV coordinates. This should provide another option for continuous delivery scripts! 

 

If you've read my interview with JAXenter, you already know  that I very much disagree with labelling Java EE as heavyweight - simply because it is not true! The latest servers from most of the Java EE vendors have been re-architected to be very light-weight on resources including memory, cpu and disc footprint. We recently did some testing of microservices implementations and many of those come in at under 50MB of RAM to run Java EE based microservices. Also, installation and configuration has been streamlined and many of the microservices versions of the products require no installation.

In this interview for JAXenter.com , Steve Millidge, the Founder of Payara and speaker at JAX 2016, talks about how to use CDI annotations in your Java EE applications, when to use which annotations, and what is automagically happening under the covers.

Steve also tells us exactly how heavyweight Java EE really is, explaining the repercussions and solutions.

 

The second release of 2016 is finally here! Payara Server 4.1.1.162 is our biggest release yet in terms of sheer number of bug fixes and new features. One of the biggest things isn't actually a new feature of Payara Server but a newly rehosted documentation, and it's where you'll find the full release notes for this version. 

Recently I attended as a speaker at my second jDays, a great conference in a great venue in Gothenburg. jDays is a fantastic conference as it is small enough to easily meet people and network and discuss tech, while at the same time big enough to run multiple tracks so there is always a session on that you’ll be interested in. 

 

---

One of the lesser known features and key benefits of Payara Server is that it provides huge flexibility when architecting topologies for High Availability and Scalability. Utilising the embedded Hazelcast Data Grid for web session and JCache clustering brings the potential of many different topologies for scale out.

 

Microservices are the latest new-but-not-really-new thing that developers are talking about, and the Java EE world is no exception. In this Devoxx 2015 talk, Mike is using some new features of Payara Server that bring the power of Hazelcast to Java EE microservices, while still keeping the overall footprint incredibly low.

 

 

 

We have already introduced Spring Boot to Payara Micro, the new fish on the block!, by implementing Spring Boot based RESTful web services and hosted on Payara Micro. While implementing it, we didn’t deal with any of the XML configurations or dependency management needed for the Spring framework with the help of  the Spring Boot