MicroProfile 1.0: HTTP is not the only way microservices communicate
MicroProfile 1.0 is intentionally feature-constrained so that a broader community can define its roadmap. The parties involved (Red Hat, IBM, TomiTribe, Payara, LJC and now SouJava) have agreed on a base set of features that defines solid and stable roots on which to grow and have added multiple member organizations and contributors. But that’s not all.
MicroProfile 1.0 is here. According to the official announcement, everything is new in this release; “more specifically, JAX-RS, CDI, JSON-P support, and samples.” To start using it, one needs to clone the conference app or samples and run them on one of the six implementations from Red Hat (WildFly Swarm), IBM (Liberty Profile), Tomitribe (Apache TomEE), Payara (Payara Micro), and Hammock.
What’s next for MicroProfile?
Mark Little, Red Hat VP of Engineering, announced in a blog post that they finished 1.0 a few weeks ahead of schedule with six different implementations and tried to answer a question that’s been on everyone’s lips from the moment this initiative was revealed: What’s next for MicroProfile?
He opined that “Java EE still has a lot more to offer microservices” and revealed that one of his “pet favourites around microservices is the move towards reactive and asynchronous.” Little added that making improvements in Java EE components/standards is “a bit of a slogan” at MicroProfile, but emphasized that nothing is set in stone and that they might eventually decide it’s not worth it and seek something else.
HTTP is not a one-size-fits-all solution
Future versions of MicroProfile may include things as asynchronous, reactive microservices, security, service discovery and some components of the NetflixOSS stack. However, Little pointed out that one should not assume HTTP is “the only way microservices communicate.” Although he acknowledged that HTTP is, in fact, convenient to use, Little emphasized that “a text-based protocol is not the way to go if you want high performance.” The solution here could be to look at messaging solutions, Little concluded.
Red Hat’s VP of Engineering also revealed that MicroProfile 1.0 is ready to be moved to a standards body. Plus, “it would seem logical for the JCP to play a role here” since this open forum is based entirely on Java EE at the moment. Little also announced that the existing MicroProfile effort will be moved to a Foundation.
MicroProfile is hosting a panel luncheon at JavaOne on Thursday, September 22nd. Join it if you want to learn more about MicroProfile 1.0 and its roadmap.