Posts tagged Payara Micro (9)
How to Run Payara Micro on Android (No Root Required)
Published on 04 Jan 2018
by Jorge Cajas
Topics:
Payara Micro,
Microservices,
How-to
|
0 Comments
Have you ever wondered how Micro is Payara Micro?
At first, this was a fun experiment installing a terminal app on my Android phone and playing around with some Linux commands. One thing lead to another and I ended up running a Payara Micro instance on my device! In this article, I'm going to show you exactly how to do that.
Kubernetes Native Discovery with Payara Micro
Published on 20 Dec 2017
by Susan Rai
Topics:
Payara Micro,
Microservices,
Hazelcast,
Clustering,
Cloud,
Kubernetes
|
1 Comment
Payara Micro supports Hazelcast out of the box, and can be used for clustering. This allows members in the cluster to distribute data between themselves, amongst other things. By default, Hazelcast comes with multiple ways to discover other members in the same network. A multicast discovery strategy is commonly used for this purpose; a multicast request is sent to all members in a network and the members respond with their IP addresses. Another strategy must be employed if a member cannot or does not wish to provide their IP address.
Speed up Microservice Development with JRebel and Payara Micro
Published on 14 Dec 2017
by Mike Croft
Topics:
Maven,
Payara Micro,
Microservices,
How-to,
Uber JAR
|
0 Comments
Admitting When You’re Wrong
Just recently, I have had to admit being wrong. Very wrong. Way back at the start of October, I was feeling the familiar sensation of panic and dread that only happens right before I need to give a presentation that includes a demo! In the end, there were major problems with the AV setup in the room I was allocated, so even arriving as early I could to set up didn’t give the techs enough time to hook up my laptop successfully.
AWS Native Discovery with Payara Micro
Published on 23 Nov 2017
by Mike Croft
Topics:
Java EE,
Payara Micro,
Microservices,
Hazelcast,
Caching,
Cloud,
Amazon Cloud,
Uber JAR,
Cloud-native
|
1 Comment
Both Payara Server and Payara Micro can cluster together and share data using Hazelcast. Out-of-the-box, there is no configuration needed, since Hazelcast uses multicast to discover and join other cluster members. However, when running in cloud environments like AWS, for example, there are a lot of things which can stop discovery being quite so straightforward. The key thing is that Multicast is not available, meaning another discovery strategy is needed; the most common generic alternative is to use TCP, but this assumes that you know at least the intended subnet that your cluster members will be in ahead of time.
Expanded Request Tracing Service in Payara Micro
Published on 21 Sep 2017
by Fabio Turizo
Topics:
What's New,
Payara Micro,
Microservices,
diagnostics,
request tracing
|
0 Comments
As previously reported on this blog, the Request Tracing Service was improved drastically in release 4.1.1.171 and implemented the configuration of a historic trace record storing for increased productivity purposes. In addition to these changes, we also made the configuration on the Request Tracing Service in Payara Micro for the same release. These changes to Payara Micro make it simpler to configure the Request Tracing Service when starting a new instance!
Payara Micro in Docker
Published on 04 Sep 2017
by Matthew Gill
Topics:
Payara Micro,
Microservices,
Docker,
Cloud
|
1 Comment
The Payara Micro 173 release had a few changes which will make the lives of Docker users easier. This blog will cover the changes which affect Payara Micro in Docker, demonstrating the following:
-
Using the new Payara Micro 5 Docker image, which provides Java EE 8 features.
-
Deploying applications without the targetted database being present.
-
Adding library JARs from the command line.
'5 ways to improve your Java EE applications in reactive way' - Ondrej Mihalyi at GeeCON 2017
Published on 30 Aug 2017
by Ondro Mihályi
Topics:
Java EE,
Payara Micro,
Microservices,
JVM
|
0 Comments
Have you ever wondered how you can improve the performance of your applications under high load? You've probably heard that reactive design can help meet better response time and make your applications more flexible. In this presentation, I will show that you don’t need to rewrite your Java EE applications from scratch to achieve that!
Using the Payara Micro Maven Plugin
Published on 03 Aug 2017
by Mike Croft
Topics:
ActiveMQ,
JMS,
Maven,
Payara Micro,
Microservices,
How-to,
Uber JAR
|
4 Comments
Payara Micro provides build tool plugins for Maven and Gradle. The plugins allows to start/stop/reload Payara Micro instance and package uber jar bundle of application. To illustrate the use of Payara Micro Maven Plugin, I'll be revisiting my earlier blog on another feature of Payara Micro - the ability to use Payara Micro as a JMS consumer.
Nadando río arriba: Avanzando con Eclipse MicroProfile y JDK8
Published on 28 Jul 2017
by Mike Croft
Topics:
What's New,
Payara Micro,
Microservices,
MicroProfile,
Eclipse,
Spanish language
|
0 Comments
Eclipse MicroProfile es una especificación para un conjunto de APIs diseñadas para construir MicroServicios. Este proyecto ha existido desde hace más de un año y es algo con lo que Payara está altamente comprometido. Los lectores a los que les gusta estar al día con las noticias desde a comunidad de Java probablemente serán conscientes de como el proyecto ha progresado a grandes saltos últimamente. Está siendo un camino largo y arduo desde la versión 1.0 a la versión 1.1 de la especificación pero, en este momento, mucho ha sido desarrollado y hay multitud de APIs actualmente en desarrollo.
Swimming Upstream: Moving Forward with Eclipse MicroProfile and JDK 8
Published on 28 Jul 2017
by Mike Croft
Topics:
What's New,
Payara Micro,
Microservices,
MicroProfile,
Eclipse
|
0 Comments
The Eclipse MicroProfile is a specification for a set of APIs appropriate to building MicroServices. The project has existed for over a year now and is something that Payara is highly committed to. Readers who like to keep up-to-date with news from the Java community will probably already be aware of how the project has progressed in leaps and bounds lately. It's been a long road from version 1.0 to version 1.1 of the specification but, in that time, a lot has developed and there are multiple APIs currently being worked on.