Welcome!

Microservices Expo Authors: Elizabeth White, Lori MacVittie, Sematext Blog, Liz McMillan, Daniel Khan

Related Topics: Java IoT, Microservices Expo, Eclipse, IoT User Interface, @CloudExpo

Java IoT: Article

The Past, Present and Future of Enterprise Java

How Java EE evolved, became a major platform specification and the direction in which it is moving forward

The Java Platform Enterprise Edition 7 specification early draft is available for download. All these years the focus was to introduce several APIs and technologies as part of the platform to make it more powerful, simple and complete. This is the first time the focus has shifted in a completely different direction - to bring in something new to the platform, apart from the enhancements to the existing technologies. In this article, we'll look at how Java EE evolved, became a major platform specification and understand the direction in which it is moving forward.

Java EE - Past
A brief look at the history of the Java EE - Java Platform Enterprise Edition specification reveals that every major release of the specification has been driven by a major theme.

A look at the specification details reveals that the theme for the first release of the specification J2EE 1.2 was to bring all enterprise specifications like Servlet, JSP, EJB, RMI, IIOP under one umbrella of specifications, the focus was to introduce support for distributed computing systems that reduce cost and complexity. The next release of the specification J2EE 1.3 was merely an enhancement to the J2EE 1.2 specification without any specific theme as such. Connector API, JMS Provider and Container Managed Persistence beans are prominent inclusions.

The theme for the next release, J2EE 1.4 was the support for Web Services. APIs supporting basic Web Services interoperability (like XML APIs) and support for tools for management and deployment were introduced. Even though J2EE platform addressed all the major requirements for developing, deploying and managing enterprise applications, the ‘Complexity' in programming business components and performance of the persistence tier remained the pain points of the J2EE platform.

So, Simplification and ease of development was the major focus in the next release - Java EE 5. Also the platform carried the new name- Java Platform for Enterprise Edition or Java EE in short. Annotation based programming made development lot easier and really addressed the issue of ‘Complexity'.  Java EE 5 makes extensive use of annotations.

The main goal of the next release of specification Java EE 6 platform was to support all technologies and framework and still continue to simplify the platform - through three interesting features: Extensibility, Profiles and Pruning. Support for RESTful Web Services was also an important inclusion in this release.

  • Extensibility - Is a mechanism which provides a way to include additional technologies and frameworks that are not part of the standard platform.
  • Profiles - Are created from Java EE APIs which will have reference to Java EE platform standard specification but on top of it, will include a sub set of Java EE Platform technologies and make the platform lightweight.
  • Pruning - Is an interesting concept, the Java EE technologies which are not relevant today (outdated- like JAX-RPC), whichever have been replaced by new set of technologies (like Entity Beans), technologies not supported well (like Deployment API) and technologies not widely deployed can be marked for removal from the platform.

Figure 1: History of Java EE

Java EE - Present
The next major release of Java EE platform is Java EE 7. The early draft is already made available for download and the final draft is expected to be released in Q1, 2013. The big focus of the platform is getting Java applications into cloud; make Java EE Platform suitable for Cloud environments. Emphasis of this specification is on cloud computing, emerging web technologies and continued improvements in ease of development. After a long gap, JMS API is expected to undergo a big overhaul. The Java EE platform provides services and developers are able to use services and consume them in a declarative manner. The main objective of the Java EE 7 platform is the platform itself becoming a service.

Java EE 7 has two primary focus areas:

  • Cloud
  • HTML 5

Cloud:
Java EE platform's container based model is well suited for Cloud environments. It is quite easy for Java EE 7 products to take the benefits of cloud environment and operate on private and public clouds and deliver their services with the help of multitenancy and elasticity. Applications deployed on the Cloud can be used by multiple tenants, however the security, isolation and QoS are guaranteed. Since container is managing the external resources like relational databases, it becomes easy for this model to be enhanced to support cloud.

The main theme would be enabling PaaS with application servers and multi-tenancy support, facilitating customers to leverage complete range of clouds - public, private and hybrid. This can be achieved by introducing new platform roles, metadata descriptor and APIs to support PaaS execution environment like multi-tenancy, resource-sharing, quality of service, elasticity and scalability. The main theme is to easily run applications on private and public clouds.

To support cloud model in the platform, most of the technologies part of this specification will get updated. Specifically, resource manager related APIs like JPA, JDBC and JMS will be updated to enable multitenancy.

HTML5:
Java EE 7 Platform will have first class support for some the recent developments in web space including HTML5 and Web Sockets. Plans are there to include HTTP Client API to support REST based Web Services.

Apart from Cloud and HTML 5 support, plans are there to include several new features discussed below as part of the platform.

Figure 2: Java EE 7 New Features

JCache (JSR 107)
JCache is a standardized caching API to enable scaling of enterprise applications through a caching layer accessible to all containers.

Concurrency Utilities for Java EE (JSR 236)
Extends the Concurrency API in Java SE and provides support for transaction aware and context aware APIs for asynchronous tasks.

Java API for JSON Processing (JSR 353)
A standardized Java API for parsing, generating, transforming and querying JSON. JSON is the lightweight data-interchange format popularly used in Web services for sending and receiving data particularly in RESTful Web Services. Due to non-availability of standardized Java API, different implementation libraries are used to produce/consume JSON response from Web services. The goal of this specification is to develop standardized Java API that will

    • Produce and Consume JSON text in a streaming way much similar to StAX
    • Build a Java Object model for JSON text using API classes much similar to DOM

However binding of JSON text to Java Objects and vice versa is also on the agenda.

Java API for WebSocket (JSR 356)
This is a standard API for creating WebSocket applications. WebSocket protocol is becoming a default standard for browsers building HTTP based applications like polling, long-polling and HTTP-streaming. This specification will provide support for WebSocket in Java EE platform for creating WebSocket for bi-directional WebSocket conversations, initiating and intercepting WebSocket events, creation and consumption of WebSocket text and binary message and working of WebSocket application within Java EE security model.

Update to Web Profile and Pruning
Java Enterprise Edition Web Profile will have JAX-RS 2.0 added to its existing set of technologies.

Some of the technologies which are outdated or not in use will be made optional as defined by the pruning process in the earlier specification (Java EE 6). Probable candidates for pruning in this release are:

  • EJB Entity Beans
  • JAX-RPC 1.1
  • JAXR 1.0

Technology Enhancements
Apart from the primary focus areas, Java EE 7 Platform has updates to the following technologies. Ease of development is the focus in all of the APIs mentioned below which have an enhancement.

  • Java Persistence API (JPA)
    • Multi-tenancy support
    • Support for stored procedures
    • Support for Schema generation
    • Update and Delete Criteria queries
    • Persistence Context synchronization
  • Java API for RESTful Web Services (JAX-RS)
    • New standardized Client API
    • Support for Hypermedia
    • Bean Validation API in JAX-RS for form and query parameters
    • Support for Asynchronous processing
  • JavaServer Faces (JSF)
    • Support for HTML 5 Forms, headings and section content model and metadata
    • New Components like FileUpload, BackButton etc.
    • Portlet Integration
  • Servlets
    • Support for NIO.2 APIs
    • Support for Async  I/O
    • Simplified asynchronous Servlets
    • Support for Java EE Concurrency  Utilities
    • Support for HTML 5
    • Support for Web Sockets
    • Support for Cloud (PaaS model for Web applications)
  • Enterprise JavaBeans (EJB)
    • Support for Cloud (Support PaaS - multi-tenancy)
    • Enhanced Interceptors
    • Simplified programming model thru' usage of annotations
    • Optional:
      • BMP /CMP
      • Web Services using JAX-RPC
  • Expression Language (EL)
    • Standalone JSR
    • Criteria based Collection selection
    • New operators
  • Java Message Service (JMS - Most mature specification, undergoing a change after 10 years - April 2002)
    • Support for Cloud (Multi-tenancy and other cloud features required...)
    • Pluggable JMS provider
    • Modest Scope
  • Context and Dependency Injection (CDI)
    • Life cycle events
    • Injection of static variables
    • Declarative package scanning
  • Bean Validation
    • Integration with other JSRs like JAX-RS, JAXB, JPA, CDI, EJB and JSF
    • Method-level validation
    • Constraint Composition

Java EE 7 Platform

Version

Java Persistence API (JPA)

2.1

Java API for RESTful Web Services (JAX-RS)

2.0

Java ServerFaces (JSF)

2.2

Java Servlets

3.1

Enterprise JavaBeans (EJB)

3.2

Expression Language (EL)

3.0

Java Message Service (JMS)

2.0

Context and Dependency Injection (CDI)

1.1

Bean Validation

1.1

Table 1: Java EE 7 - Enhancements to Technologies

Java EE - Future
Modularity

Support for modularity and versioning capabilities will be included in the future version. This depends on the modularity work happening on Java SE. Release of Java SE 8 will have an alignment with modularity feature in Java EE specification.

Cloud
As per the latest press release a major disappointment comes on the release of the Java EE 7 specification. As per the blogspot of Linda DeMichiel-  the specification lead for Java EE platform 7, the project will be delayed for another year if support for PaaS environment and multi-tenancy has to be included. So the complete support for PaaS enablement and multi-tenancy will see the light only during the next release of Java EE - Java EE 8.

Linda DeMichiel wrote on her blog - "Partially this has been due to a lack of maturity in the space for provisioning, multi-tenancy, elasticity, and the deployment of applications in the cloud. And partially it is due to our conservative approach in trying to get things "right" in view of limited industry experience in the cloud area when we started this work. Because of this, we believe that providing solid support for standardized PaaS-based programming and multi-tenancy would delay the release of Java EE 7 until the spring of 2014 - that is, two years from now and over a year behind schedule. In our opinion, that is way too long.

We have therefore proposed to the Java EE 7 Expert Group that we adjust our course of action - namely, stick to our current target release dates, and defer the remaining aspects of our agenda for PaaS enablement and multi-tenancy support to Java EE 8.".

However there are vendors like Red Hat and CloudBees who already support some parts of Java EE specifications in the Cloud environment. Experience of the vendors in this area will help in standardization of the specification better.

Conclusion
With the cloud support removed, Java EE 7 loses the most prominent feature, but still tries to make the release interesting with lot of additions and enhancements to existing APIs like Client APIs in JAX-RS, updated JMS API, and support for HTML 5 and updates to EL, JPA, CDI and JSF.

So the belief is Java EE 8 will provide full standardization support for cloud although the current version might not be completely ready. So "PaaS enablement and support for SaaS model" and "Modularity" will be two interesting features to look out for in the future version of the Java Platform Enterprise Edition- Java EE 8.

The contents represented in this article are purely the author's view.

Acknowledgments
The author would like to acknowledge and sincerely thank Mr. SV Subrahmanya, VP, E&R for the idea, guidance, support and constant encouragement and Mr. Piram Manickam, Senior Architect for his valuable suggestions and review.

References

  1. JCP - JSR 342: Java EE 7 (http://www.jcp.org/en/jsr/proposalDetails?id=342)
  2. JCP - Concurrency Utilities for Java EE (http://www.jcp.org/en/jsr/detail?id=236 )
  3. JCP - JCache (http://www.jcp.org/en/jsr/detail?id=236 )
  4. Arun Gupta's Blog (https://blogs.oracle.com/arungupta/entry/java_ee_7_key_features )
  5. Linda DeMichiel' s Blog (https://blogs.oracle.com/theaquarium/entry/java_ee_7_roadmap )

More Stories By S Sangeetha

S Sangeetha is a Senior Technical Architect at the E-Commerce Research Labs at Infosys Limited. She has over 15 years of experience in architecture, design and development of enterprise Java applications. She is also involved in enhancing the technical skills of Architects at Infosys. She has co-authored a book on ‘J2EE Architecture’ and also has written numerous articles on Java for various online Java forums like JavaWorld, java.net, DevX.com and internet.com. She can be reached at [email protected]

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
SYS-CON Events announced today that Isomorphic Software will exhibit at DevOps Summit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Isomorphic Software provides the SmartClient HTML5/AJAX platform, the most advanced technology for building rich, cutting-edge enterprise web applications for desktop and mobile. SmartClient combines the productivity and performance of traditional desktop software with the simp...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Node.js and io.js are increasingly being used to run JavaScript on the server side for many types of applications, such as websites, real-time messaging and controllers for small devices with limited resources. For DevOps it is crucial to monitor the whole application stack and Node.js is rapidly becoming an important part of the stack in many organizations. Sematext has historically had a strong support for monitoring big data applications such as Elastic (aka Elasticsearch), Cassandra, Solr, S...
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo Silicon Valley Call for Papers is now open.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
Ovum, a leading technology analyst firm, has published an in-depth report, Ovum Decision Matrix: Selecting a DevOps Release Management Solution, 2016–17. The report focuses on the automation aspects of DevOps, Release Management and compares solutions from the leading vendors.
No matter how well-built your applications are, countless issues can cause performance problems, putting the platforms they are running on under scrutiny. If you've moved to Node.js to power your applications, you may be at risk of these issues calling your choice into question. How do you identify vulnerabilities and mitigate risk to take the focus off troubleshooting the technology and back where it belongs, on innovation? There is no doubt that Node.js is one of today's leading platforms of ...
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
SYS-CON Events announced today that LeaseWeb USA, a cloud Infrastructure-as-a-Service (IaaS) provider, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. LeaseWeb is one of the world's largest hosting brands. The company helps customers define, develop and deploy IT infrastructure tailored to their exact business needs, by combining various kinds cloud solutions.
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
DevOps at Cloud Expo – being held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Am...

Let's just nip the conflation of these terms in the bud, shall we?

"MIcro" is big these days. Both microservices and microsegmentation are having and will continue to have an impact on data center architecture, but not necessarily for the same reasons. There's a growing trend in which folks - particularly those with a network background - conflate the two and use them to mean the same thing.

They are not.

One is about the application. The other, the network. T...

The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Digital Transformation, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportuni...
If you are within a stones throw of the DevOps marketplace you have undoubtably noticed the growing trend in Microservices. Whether you have been staying up to date with the latest articles and blogs or you just read the definition for the first time, these 5 Microservices Resources You Need In Your Life will guide you through the ins and outs of Microservices in today’s world.
Before becoming a developer, I was in the high school band. I played several brass instruments - including French horn and cornet - as well as keyboards in the jazz stage band. A musician and a nerd, what can I say? I even dabbled in writing music for the band. Okay, mostly I wrote arrangements of pop music, so the band could keep the crowd entertained during Friday night football games. What struck me then was that, to write parts for all the instruments - brass, woodwind, percussion, even k...
This digest provides an overview of good resources that are well worth reading. We’ll be updating this page as new content becomes available, so I suggest you bookmark it. Also, expect more digests to come on different topics that make all of our IT-hearts go boom!
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor – all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
In his session at @DevOpsSummit at 19th Cloud Expo, Yoseph Reuveni, Director of Software Engineering at Jet.com, will discuss Jet.com's journey into containerizing Microsoft-based technologies like C# and F# into Docker. He will talk about lessons learned and challenges faced, the Mono framework tryout and how they deployed everything into Azure cloud. Yoseph Reuveni is a technology leader with unique experience developing and running high throughput (over 1M tps) distributed systems with extre...