As we are at the start of a New Year and it is traditional to gather your thoughts and put in place New Year resolutions and plans, I thought I would share with our Community and Customers the plans for Payara in 2018.

お楽しみの、喜びの、奉仕の、そして釣りの (違った、最後のは私が付け加えただけです) 季節がやってきました。そして世界中の皆様、このお休みに (訳注: イギリスはクリスマスと翌日が祝日です) Payara Server 5 の最初のベータ・リリースをお届けします。ダウンロードはこちらからどうぞ。本当は何が欲しかったのか、私は知っているんですよ。

 Read this post in English

It’s the season of joy, cheer, giving, and fish (no, I haven’t just added the last one) and so as a gift to the world we’ve just released the first Beta release of Payara Server 5 in time for the holidays - download here. I know, it’s exactly what you wanted.

Read this post in Japanese

We’re very excited to announce our new Payara Team member - Kenji Hasunuma - who joined us at the beginning of November! If you've been an active Java EE & Payara community member in Japan I'm sure you recongnize his name :) 

Read along to find out more about Kenji and what he’ll be working on at Payara.

We're excited to announce that the second Alpha release of Payara Server 5 is now available for download! We highly encourage you to give it a go, test it out and let us know what further improvements are needed. 

A crucial component in many web applications is the use of a database. The chances of using JDBC directly or indirectly to access a relational database (through JPA or other ORM frameworks) on these applications are quite high. A common problem when dealing with relational databases is dealing with SQL queries or statements that take too much time to resolve, thus causing your application to be considered slow in producing results to the user. It's usually better to detect these issues preemptively, before sub-par performance damages your application, and Payara Server has you covered!

One of the core steps in every continuous integration process is running integration tests for your application. Unlike vanilla unit tests, integration tests allow you to assess the state of your applications or systems by testing all of its components together (modules, databases, messaging, etc.) and verifying that they work correctly as a whole unit. Needless to say, integration tests are more complex that simple unit tests, have a larger footprint, take more time and are usually saved to test full releases or major changes to implementations.