DevNation during the last General Assembly, Red Hat, IBM, Tomitribe, Payara and London Java CommunityAnnounceCreateMicroProfileThis is a try to create a vendor-neutral framework for the use of micro-services Java EE technologies new program. The goal is to release the first public version in September 2016, so that developers can use Java to create a more easily portable micro-services. In this regard, Martijn Verburg from London Java Community had this to say:
Our initial goal is most familiar with enterprise-class Java (if you wish, you can say Java EE) developers off the ground, so that they can in a vendor-independent manner (in the Java EE world, this is their habit way) using micro-services. Then there goal is to allow the developer community to really push what they consider micro service runtime / API needed something, so that suppliers do not have to & ldquo; guess & rdquo; a user may want features such as security, or logs, or service discovery and so on. This will be determined entirely by MicroProfile community, they will help to define what should be included and what should be removed.
For developers, Java EE provides some clear benefits. It provides a stable libraries, these libraries through the development, integration and testing, out of the box. In addition, since there are many Java EE container available, so developers can code and platform decisions will be considered separately. However, Java EE rather bulky, and follow a unified standard, which means that it develops very slowly; in terms of stability, which is an advantage, but it is not suitable for fast-paced micro-services fields. Therefore, to create a similar communityWildFly Swarm OrWebSphere Liberty Such a solution that allows developers to create applications more lightweight, but still based on Java EE components. Such framework has helped to bridge the gap between innovation and standards, but it also has its own problems: Since each frame is individually created, application porting from one frame to another frame is difficult.
This is the reason MicroProfile arise. Create a standard framework, based on the definition of micro-services based Java EE applications, enables suppliers to develop such standards compatible application server, for developers to provide a coherent ecosystem container, so that they do not have to modify the application more choices. MicroProfile official version is expected to released in September 2016, before what is not yet determined, but initial presentation show, MicroProfile will to JAX-RS, CDI, JSON-P as well as any other community deems necessary technology.
Although MicroProfile and existing Web Profile were similar but not the same way they are used. Web Profile as a subset of Java EE and created specifically for the Web application, it creates two main reasons: more lightweight framework and simpler supplier verification process. At first glance, one might think MicroProfile is the next step, Web Profile micro subset of services; however, this is not entirely true that there are several reasons. On the one hand, the preliminary discussion note,MicroProfile may include some Java EE technologies even none coveredLike Vert.x; on the other hand, created a formal Java standards process may be too slow to meet the needs of a rapidly growing industry.
The first step is whether MicroProfile end Java EE remains to be seen. However, MicroProfile brought innovation and vitality should provide some fresh air to the enterprise-class Java capabilities, taking into accountIn its most recent stagnation concerns arising, Which it is now urgently needed.