Interviews of Payara Users in Japan

HASUNUMA KenjiGlassFish Users Group Japank.hasunuma@coppermine.jp

Interviewer

Kenji Hasunuma

@khasunuma

Interviewees

Interview #1

Taichi Uragami

@backpaper0

Please introduce yourself.

I work for a software vendor in Osaka.

My experience of Java EE is since 2010. At that time, there was Java EE 6 with GlassFish v3.

I've been using Payara from 2015, and I wrote an article about creating UberJAR using Payara in summer 2016.

Recently I learn Spring so I don't use Payara frequently.

But I often maintain JAX-RS applications running on GlassFish or Payara.

You wrote about Payara on Docker your blog entry in last winter.

Please tell me your impression.

It's how to run simple application on Payara Micro using official Docker image.

I had a lot of fun because it's so easy to run.

Nothing to say, Payara Micro is so easy and efficiently without Docker, I recommend it if you've used yet.

You are most famous JAX-RS specialist in Japan.

Please tell me your opinion to Payara as a platform of JAX-RS.

Really? I don't know I'm famous or not.

I believe Payara is the best application server to use latest version of Jersey, RI of JAX-RS. (I like Jersey so much)

When I used GlassFish, I was frustrated. Because it was updated irregularly and I couldn't use the latest Jersey.

Meanwhile, Payara is updated frequently. Thus l am released such a frustration.

What do you hope Payara's future?

As mentioned earlier, I learn Spring now and it's weight is increasing day by day.

I hope that Payara make Java EE more exciting and progress with Spring as rival.

And I hope also both Payara and WildFly improve each other as Java EE servers.

Thank you so much for your interview and coming from Osaka!

Interview #2

Masatoshi Tada

@suke_masa

Please introduce yourself.

I work at CASAREAL,inc. and teach Java EE and Spring Framework.

I always use Payara in Java EE training cource.

Why you know Payara?

I knew Payara on Twitter. Perhaps it's Kenji's tweets.

The past days, I used GlassFish in training course. But I was uneasy.

Because it's update was irregular and bug fixes were too late.

Payara has almost common architecture with GlassFish, so it needs no cost to revise sample programs.

And it have many bug fixes and new features, thus it is very useful for training.

You report many issues.

Please tell me tips to report by English.

When I report an issue, I make a minimum samples to reproduce and upload it.

Writing English is often difficult.

But because Java is our common language, it is easy to tell the issues to Payara team.

I write mainly a way to reproduce in an issue.

And to attach screenshots, we can communicate without long description in English.

Now Payara provides a template of issues, I follow it. For example, describe the environment.

What do you hope Payara's future?

I wish Payara is more progress and keeping compatibility with GlassFish.

I want both GlassFish and Payara provides patches each other, then it make improvement Payara, GlassFish and Java EE.

Java EE 8 will released soon. So I want Payara based GlassFish 5 earlier.

Thank you for your interview.

Interview #3

Norito Agetsuma

@n_agetsu

Please introduce yourself.

I work at NTT Comware Corporation.

I am in charge of troubleshooting of Java-based systems, and recently I support for Elastic stack.

I heard you're a troubleshooter.

Then you think what's application server Payara from troubleshooter's eyes?

I welcome to Payara because of it's open source.

If some system is happened a major trouble, we only wait from the vendor's support in case of closed source.

And the support requires logs, resources, etc.

But we are often forbitten to send logs because of various restriction of systems, thus we cannot consult the vendors.

OSS have nothing of such a limit.

Recently release of Payara improves monitoring and management features.

What you think about them?

I give my honest opinion, their are not unique.

Notifier features and logging for threshold are already other production application servers.

For example, WebLogic's diagnostic framework is famous one.

Although Payara is a match for them however it's OSS.

What do you hope Payara's future?

Quality First!

GlassFish 4 has stagnated many issues.

It's needed bug fixed frequently and gain users' reliance.

So Payara may beets other production servers.

And, It's my opinion, I hope Payara includes candidate APIs of Java EE or MicroProfile as preview and contributes to standardize them.

Other servers includes new Java EE APIs after it's release now.

But Payara leads new standardize, I hope.

Thank you for your interview however you're so busy.

Interview #4

Ippei "Kazuhira" Matsushima

@Kazuhira_r

Please introduce yourself.

I develop Java application in daily work.

Side by side with, I write technology blog in Japanese.

My blog's entries are mainly Java, Java EE and In-memory data grid.

I'm interested in In-memory data grid and almost entry is about it.

I have written about Hazelcast blog entries and sample codes.

The activity is rated high by Hazelcast as "Hazelcast Heroes"

I often picked up Payara with Hazelcast and wrote some entries about Payara using Hazelcast.

You know "Hazelcast Heroes", do you know Payara via Hazelcast?

Tell the truth, I knew Payara because of JCache.

I've been interested in JCache before version 1.0, and watched implementations of JCache and which implementation is used by Java EE servers.

When I knew Payara adopted Hazelcast as JCache implememtation, I surprised the choice.

But now I believe it's rational selection because of Hazelcast's popularity.

Your blog's topics are spread and there are many entries about Payara and Hazelcast.

Which entries do you gave impression yourself?

There are two entries.

At the first, it's only Hazelcast, it's the entries that explanation of internal data structure, classes using network, behavior of Hazelcast.

I wrote them for request of a Japanese Payara user.

It's my thought, Japanese Payara users unfamiliar with in-memory data grid, so I'm grad if the entries help them.

The second, the entry about Clustered CDI Event Bus of Payara.

Payara mainly uses Hazelcast for JCache, Session replications, Clustering.

I think the feature is good integration of Hazelcast Topic and Java EE CDI.

When I wrote it, I run it and view Payara's code. I was impressed with the way.

What do you hope future of Payara and Hazelcast?

Now Payara and Hazelcast is good for integration of clustering, data sharing beyond the node, etc.

I think it lack use cases and examples.

I wish that Payara show many use cases and patterns of integration of Payara and Hazelcast as possible.

I think it helps many users.

For examples, how to build Payara clusters on the cloud, Using Hazelcast's distributed data structure from Payara, updating Payara clustering.

Making Payara cluster by Hazelcast is very easy, but many Japanese users are no idea of practical use.

I hope Payara blog publishes such know-how.

I expect Payara not only Java EE but also growing more and more.

Thank you for your interview. I'm sorry for such short notice.

Thank you so much for all interviewees