Posts from Ondro Mihályi

Photo of Ondro Mihályi
Ondro is a software developer and consultant specializing in combining standard and proven tools to solve new and challenging problems. He's been developing in Java for over 10 years. He works as a Service Engineer for Payara Services, helping their customers and the wider Java community with their projects based on the Payara Platform. As an experienced Java developer and trainer, he's also helped companies to build and educate their development teams and improve their development processes. He's a core member of several open source projects, inclluding MicroProfile and Jakarta EE. He’s a leader of Czech JUG and a Java Champion.

Find me on:

A Step-by-Step Guide from Traditional Java EE to Reactive Microservice Design

A workshop given at JPrime conference in May 2018.

Have you wondered how you can improve the design of your applications to improve its performance? You probably heard that reactive design can help achieve better response time and make your applications more flexible. But you’re asking: Do I need to rewrite my applications from scratch? Do I need to learn a new framework for all that? The answer is no, especially if your application is built on top of Java EE and Java 8.

Flexibility First - Payara Docker Images Allow a Completely Custom Start-up Configuration

We work hard to make Payara Server robust, reliable, and innovative so that it's perfect for production deployments. But we never forget about the users and developers. For them, we target flexibility and ease of use in every new feature we add and every tool in the ecosystem we maintain. Our Payara Docker images are an example of it and we're happy about the positive feedback from the user community we receive, as well as the constructive suggestions that help us improve user experience in the future.

 

Recent Additions in MicroProfile Config 1.1

Configuration is an important aspect of programming. However, a standard approach to it has been missing in Java for a long time. A year ago, the MicroProfile project decided to change that. I'm glad I could be part of it and help design the new API. One year later, a common configuration API aiming to set a standard is a reality, with several released versions and multiple projects that provide it. Payara Server and Payara Micro have supported MicroProfile Config API since version 4.1.2.173. We added support for Config 1.1 in version 4.1.2.174 and completed the support for all Eclipse MicroProfile 1.2 features in version 4.1.2.181. So let's summarize what's new since Config 1.0.

Using HotswapAgent to Speed up Development

As a Java EE developer, I sometimes envy how fast it’s possible to see the result of a code change in a running application with interpreted languages like PHP or JavaScript. With Java, it’s always necessary to rebuild the source code in bytecode, which can be then safely updated only by restarting the whole application. And all developers know that restoring the desired state of the application after a fresh restart takes time and is tedious.

'5 ways to improve your Java EE applications in reactive way' - Ondrej Mihalyi at GeeCON 2017

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!

 

Oracle Code Prague - Impressions & Videos

At the end of April I had a pleasure to speak at the Oracle Code event in Prague. 

Oracle Code is a new series of free events, hosted in different locations around the world and aimed at Java developers, giving them an opportunity to learn about the latest dev technologies, practices and trends.

Payara Server 171 - Expanded Request Tracing

Since being introduced as a technical preview, the Request Tracing Service has been improved and polished to meet production quality requirements. In the latest Payara Server version 171, it was extended to allow tracing of more request types and more events that happen during the requests. It can also remember traces of the slowest 20 requests for viewing them later, though the number stored can be increased or decreased.