Community

WebSphere Liberty: Different from traditional WebSphere

We’ve reviewed how WebSphere Liberty differs from older Java EE application server products, which makes it better suited for cloud applications and microservices. Is it the same as WebSphere Application Server (WAS)? And what are the different options for creating a Liberty runtime?

In this excerpt from “Java EE, the next inception: A primer to WebSphere Liberty for Java EE developers,” we’ll explore how Liberty compares to traditional WAS. Next, we’ll look at the difference between a profile and a server.

To start at the beginning of this series, see WebSphere Liberty: Developing Java EE applications for the cloud.


Difference between Liberty and WebSphere Application Server

WebSphere Application Server is made up of two application server runtime environments called profiles:

  • Traditional WAS (sometimes referred to as WebSphere Application Server “classic” or “full profile”) – The original architecture of WebSphere Application Server that started in 1998 with Servlet Express v1.0 and evolved into an industrial-strength Java EE container.
  • Liberty (sometimes called “WAS Liberty” or “Liberty profile”) – The next generation Java EE container architecture, introduced in WebSphere Application Server v8.5.0 in 2013, designed to be highly composable, to start faster, use less memory, and scale better.

Which WebSphere Application Server are you familiar with? When you’re using a WebSphere Application Server Network Deployment cell, each cluster member runs in an installation of traditional WAS. Even though Liberty is part of the WebSphere Application Server product, you may not have used it yet.

As you’ll see, Liberty’s runtime is very compact and lightweight, making it particularly well-suited for virtualized infrastructure and cloud computing, for lightweight containers, and also for devices in the Internet of Things.

Liberty is available packaged in several different platforms. As of this writing, they are:

  • Liberty profile – Part of WebSphere Application Server and available separately, for installation on an on-premise computer, including installing it locally on your laptop for development.
  • Liberty Docker images – The websphere-liberty images that run Liberty in Docker containers.
  • Bluemix instant runtime – The Liberty for Java runtime in Bluemix, built using the IBM WebSphere Application Server Liberty Buildpack for Cloud Foundry.
  • Bluemix container – The IBM Liberty Image (ibmliberty), the websphere-liberty image optimized for running in Bluemix.

For a given version of Liberty (such as v8.5.5.6), each of these installs provides equivalent, nearly identical functionality. The main difference is that the buildpack does not include Liberty features that are not used in a cloud environment.

—Bobby Woolf (@bobby_woolf)

Share this post:

Share on LinkedIn

Add Comment
No Comments

Leave a Reply

Your email address will not be published.Required fields are marked *

More Community Stories

Building a Java EE app on IBM Bluemix Using Watson and Cloudant

This how-to creates an example app using Java, Cloudant, and Watson. Imagine that you're a talent manager at a growing tech startup. You're looking for a new hire that would be a good fit on your team but the company is so popular that you have a huge inventory of resumes to sort through. With Watson services, you can solve for a problem like, “I’m looking for another developer like “[insert cool employee]” or “Find me a Developer like Craig Smith”.

End of beta – BigInsights for Apache Hadoop Basic plan

We have had a successful Beta of the Basic plan on BigInsights for Apache Hadoop. We’ve incorporated your feedback into the Basic plan that was launched in August this year. The Beta of the Basic plan is retired; the Basic Plan will be available as a GA offering and we will share updates on this soon. The Enterprise Plan is unchanged.

Bluemix Secure Gateway = secure access to data and applications across environments

With the prevalence of hybrid cloud environments, many of our databases and applications are unreachable due to security restrictions and firewalls. We need an easy, scalable, and secure way to access these databases and systems. The Bluemix Secure Gateway Service easily enables secure access to data and applications across environments, whether it be from on-premises to the cloud, one cloud to another cloud, or just from your laptop to the cloud. This post explains the basic flow of using the Secure Gateway service and describes current and future features.