Interview with Graham Charters and Katherine Stanley

“Think of Eclipse MicroProfile as two things: The project and the technology set”

JAXenter Editorial Team
Eclipse MicroProfile
Graham Charters and Katherine Stanley at JAX London 2017

A lot has happened lately in the Eclipse MicroProfile world: they revamped the logo, released 1.2 and welcomed Oracle to its community. JAXenter editor Gabriela Motroc caught up with Graham Charters and Katherine Stanley at JAX London 2017 to talk about the benefits Java EE brings to a microservices architecture, Java EE 8 and the future of both EE4J and Eclipse MicroProfile.

“There is going to be a lot of overlap between the Eclipse MicroProfile community and the EE4J community”

After Oracle decided to move Java EE technologies to the Eclipse Foundation, discussions about merging EE4J and Eclipse Microprofile started to appear. Senior Director of Product Management for Middleware at Red Hat told JAXenter in mid-September that “Red Hat are definitely interested in aligning the two initiatives and are willing to invest time and energy to make that happen.” However, he pointed out that the Eclipse MicroProfile community will “dictate its own future” and the same goes for the EE4J community. 

But will both projects move forward now that they reside under the same roof? According to the blog post announcing the official involvement of Oracle in the Eclipse MicroProfile community, the answer is “yes”.

Eclipse MicroProfile and EE4J both promote Enterprise Java in the areas of microservices, server-side and cloud-native applications. The Java EE community has focused on standards, while MicroProfile has focused on rapid collaborative innovation. Both want to facilitate user choice through multiple implementations and to be agile and more responsive to developers. There are various ways these goals can align as both open source projects move forward.

SEE ALSO: “We should use Java EE 8 in present tense and EE4J when speaking of the next release”


JAXenter editor Gabriela Motroc talked with Graham Charters and Katherine Stanley at JAX London 2017 about the future of Eclipse MicroProfile and EE4J. In short, EE4J needs to become established first and then the community can decide whether Eclipse MicroProfile and EE4J should be merged or not.

However, Graham encourages us to think of Eclipse MicroProfile as

  1. The project
  2. The technology set, which will continue to make sense irrespective of what happens next

For more information about the future of Eclipse MicroProfile, the benefits of an open source Java EE and the Java EE 8 release, check out the interview. 

SEE ALSO: Eclipse MicroProfile 1.2 is here: Updates and benefits

For more information about the motivation behind Eclipse MicroProfile and what the project has achieved since its creation, check out this article by Martijn Verburg, CEO and co-founder of jClarity. 


Graham Charters works as a Developer Advocate in the WebSphere Applications Server development team based at IBM’s R&D Laboratory in Hursley, UK. He takes a keen interest in emerging technologies and practices and in particular programming models. His past exploits include establishing and contributing to open source projects in PHP and at Apache and participation in, and leading, industry standards at OASIS and the OSGi Alliance.

Katherine Stanley is a Software Engineer in the IBM Java Cloud Native development team based in the UK. She works on the Java developer experience in the IBM Cloud and specializes in microservices architectures. She has co-authored an IBM Redbook on Java microservices and has created samples to demonstrate industry best practices. She also works on the open source microservice project Game On. Katherine has given workshops and presentations at various European conferences, including DevoxxUK and OSCON in London and JFokus in Sweden.


Inline Feedbacks
View all comments