今日、マイクロサービスのコンセプトは単に新しいだけではなくなっています。DevOpsの登場、コンテナ技術ブーム、デプロイ自動化ツールによって、マイクロサービスは開発者が手掛けるアプリケーションの構造を変えつつあります。マイクロサービスはJava EE開発者にとっていかにして有効な選択肢となり得るのか、そしてPayara Microとそれが提供する完璧なプラットフォームによってどのようなメリットが得られるのかについてみてゆきましょう。

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.

Recently I was tasked with preparing a presentation on an update to Jakarta EE and Eclipse MicroProfile® and it got me thinking about the organisation and structure involved in this huge effort to transform Java EE into a truly open source standard under the Eclipse Foundation. While organising my thoughts I put together a picture showing the structure and tensions of this undertaking to help people understand what various groups do and perhaps how better to get involved. The structure and governance is evolving as I write this so I may not get everything right. 

Introduction : 

Java EE Security API (JSR 375) :

The Java EE Security API 1.0 is a new spec for Java EE 8 that aims to bridge some of the gaps that have traditionally been left unspecified and provides the new way to define or configure identity stores and authentication mechanisms.  

It's here! The Eclipse Foundation has announced the future of Java EE with the release of Jakarta EE ; a cloud-native Java and an open source governance model. As enterprises modernize their infrastructure for cloud, microservices and containers, the technological transformation requires a new governance model that provides faster release cycles to keep pace with innovation, along with an open source, community-driven evolution of the platform.

It is highly likely that most people involved in the Java EE community are already aware of the open sourcing of Java EE and the move to the Eclipse Foundation. For those unaware, however, here's a quick primer:

There have been a lot of really great updates coming out of the EE4J project recently and as far as I can see, the project is progressing nicely given the size and complexity of the undertaking.

Thanks to Sun Microsystems, Java has an open source history dating back over ten years. 

In 2006, the OpenJDK project was announced.  It took a while to remove some lingering proprietary components but, with build 53 of OpenJDK 7, we finally had a fully open source version of the JDK.  This also became the source code for the reference implementation of the Java SE standard as of Java SE 7.

(Guest blog)

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.