Taking Jakarta EE into the public cloud is a breeze thanks to Jemo

Eclipse Jemo set to provide a new platform for multi-cloud native apps

Jane Elizabeth
Eclipse Jemo
Shutterstock / Chaykovsky Igor

Proposal accepted: Eclipse Foundation said yes to multi-cloud FaaS implementation for JVM based languages. Eclipse Jemo lets developers utilize cloud native apps across multiple clouds. No storm clouds on this horizon!

Today, we’re taking a look at one of the newest additions to the Eclipse Foundation ecosystem: Eclipse Jemo!

Eclipse Jemo was accepted to the Eclipse Foundation in late 2018. Jemo will provide a platform, frameworks, and runtime support for developers looking to create cloud native apps on multiple clouds.

This means there will be a true, multi-cloud FaaS implementation for JVM-based languages once Jemo is up and running.

Eclipse Jemo

Initially a part of Cloudreach, Jemo started life as an iPaaS (Integration Platform as a Service) offering for Salesforce. However, in order to increase adoption, Cloudreach is open sourcing it through Eclipse.

Eclipse Jemo is designed to give developers cloud native apps with a number of support structures to make multi-cloud implementations headache free. While it is still in the process of joining the Eclipse Foundation, the scope is already settled to include:

  • An application runtime
  • Event driven paradigm for multi-cloud deployment
  • UI framework for creating single-page web apps without needing a background in JavaScript or frontend development
  • A common runtime framework for the cloud that is provider agnostic
  • Runtime implementations for all major cloud service providers
  • Monitoring, logging, and analytics for advanced management

Developers familiar with Kubernetes will recognize the same event-driven FaaS development patterns for service offerings.  What’s more, Eclipse Jemo will be able to provide support for popular Java frameworks like MicroProfile, Spring, Jakarta EE, and more by using runtime implementations.

Eclipse Jemo follows the write once, run everywhere ethos of the JVM. It’s explicitly designed to avoid vendor lock-in for the various cloud service providers. No matter if you use Amazon AWS, Microsoft Azure, or Google Cloud Platform, Jemo harnesses the underlying PaaS services. Developers can then build their apps without worrying about getting stuck to a specific provider.

SEE ALSO: Eclipse IDE 2018-12 arrives with some major improvements

Moving forward with Eclipse Jemo

This project is very much a work in progress. However, by taking a look at the project schedule, things should be happening fairly quickly over the next year:

  • Initial Release: Q1 FY19 – release of current functionality with new OSS branding and licensing as well as release of documentation reworked with OSS branding.
  • Release 0.2 – Q2 FY19 – release of runtime support for GCP, Support for Java 11
  • Release 0.3 – Q3 FY19 – Addition of development patterns for Stream processing and BigData systems
  • Release 0.4 – Q4 FY19 – Addition of HTTP/2 (Async HTTP) and WebSocket patterns, Enhanced monitoring and management through JMX
  • Release 0.5 – Q1 FY20 – Addition of patterns to support Machine/Deep Learning and Virtual Assistants (Google, Cortana, Alexa)

Future features include things like runtime support for GCP, enhanced monitoring via JMX, improved support for Java 11, as well as development patterns for Stream processing, BigData, HTTP/2,  and WebSockets.

More information about the Eclipse Jemo project can be found here.

Jane Elizabeth
Jane Elizabeth is an assistant editor for

Inline Feedbacks
View all comments