The goal of MicroProfile.IO is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space.

Java EE 8 fully supports asynchronous handling of REST requests and responses, on both client and server side. This is useful to optimize throughput of an application or even when adopting reactive principles. MicroProfile type-safe REST client API also supports this concept to allow you to call REST services asynchronously with a much more straightforward way with plain Java interfaces.

I've been to Sofia, Bulgaria, a couple of times already. It all started with the Java2Days organizers inviting the Payara team to give a talk 2 years ago. But this time it was something special. The organizers joined forces with other IT conferences and prepared a special edition for its 10th anniversary in what is probably the largest building in Bulgaria - the National Palace of Culture.

 

For a long time, the Java EE security system has had a quite cool, but   woefully underused, feature; pluggable authorization modules. The authorization modules are provided by a specification called Java Authorization Contract for Containers, aka  JACC. 

 

It seems like Microservices architecture is almost everywhere these days. For a long time, I used to have a feeling that many people talked about it but very few use it. So I decided to find out how to get the most out of Microservices. I've studied this architecture a lot, experimented with the technology created specifically for Microservices and talked to other people who knew more than me. This how I've met some incredible people. And it's also a reason why I've joined forces with Reza Rahman and Ivar Grimstad to create a Hands-on Lab about our findings, which we'll present at Oracle Code One this year.

今日、マイクロサービスのコンセプトは単に新しいだけではなくなっています。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.