Thursday Mar 28, 2013

A Perception Frozen in Time

I haven't blogged in roughly a year. However, the InfoWorld article "Can TomEE save Java EE" brought me out of my blogging hiatus.  Putting the title in context,  driving controversy drives clicks and ad revenue. I grok that. The lead-in paragraph, however, talks about Java EE being frozen in time and those who care about appservers sitting in grey cubicles. After reading the article, I picked myself up and dusted myself off.  Not from being knocked down, mind you, but from a fit of ROFL at the author's portrayal of Java EE. Now to defend the faith.

As a disclaimer, I lead the Java EE and GlassFish Server Product Management team at Oracle. As another disclaimer, I haven't worked in a cubicle in over 7 years :-) There are two ways I am going to approach an opposing view - the Java EE programming model and Java EE implementations.

From a programming model perspective, there is no doubt that J2SE 1.4 + J2EE had its problems back in 1999-2003. It was complex. EJB 1.x/2.x and the persistence model spawned Hibernate and Spring. In 2006, Java SE 5 + Java EE 5 introduced annotated POJOs, where transactional business logic and persistence were greatly simplified.  In 2009, Java EE 6 added the Web Profile, enabling, for example, Caucho Resin and Apache TomEE to more directly influence the direction of Java EE with their own implementations. In 2013, on the verge of Java EE 7, the programming model is simplified even further with new and enhanced features driven by annotated POJOs.  It doesn't get much simpler than
@Transactional @WebSocketEndpoint("/myEndpoint" ), does it? IDE's have all these wizards to help you become more productive, yet nine times out of ten I keep falling back to New->Java Class and tacking on the annotations I need. EJBs, Entities, Servlets, CDI - annotated POJOs. This POJO-based approach to development makes solving simple problems easy and the overall platform makes solving the wickedly hard problems possible.

From an implementation perspective, vendors have moved from monolithic J2EE runtimes toJava EE Compatible modular Java EE runtimes that start in seconds, whether due to OSGi or other innovative modular systems.  GlassFish Server, the Java EE reference implementations, introduced modularity in 2008. To put this in perspective, that's 2 years before Apple (re)introduced the world to tablet computing with the iPad.  This was partially driven by customer demand and competitive pressures, partially by the introduction of the Web Profile, which required vendors to modularize their appservers if they wanted both  full Java EE runtime and Web Profile distributions.  Of course, Java EE implementations follow a bit behind the latest standard. Many organizations don't like change due to introduced risk and therefor continue run older versions of appservers. However, Java EE's backwards compatibility and well-defined deprecation strategy makes moving forward as easy as possible.  Either way, vendors support them.

I have a tremendous amount of respect for David Blevins for his work in the Java Community Process and taking on TomEE as a Java EE compatible distribution. He also separated himself from the author's position in the article with his own post and takes the high road. Thanks, David.

To sum it up, Java EE is an easy platform to develop to, and implementations have become pretty darn lightweight and modular.  What is frozen in time is the author's perception that Java EE needs saving.

Wednesday Mar 02, 2011

GlassFish Server Load Balancing Plugin Installation & Setup

With the recent launch of Oracle GlassFish Server 3.1, we have made some significant improvements to our clustering implementation such as improved performance and smarter failover.

However, clustering is pretty useless without a means to failover from a failed node to an active node - with the user being oblivious to the failure.  The good news is that we have also updated GlassFish Server Control to include the Load Balancer Configurator and load balancing plugin.  Check out the compatibility matrix for supported web servers and platforms (.xls).

To help those who want to use the GlassFish Server load balancing plugin, I've recorded a 30 minute tutorial/demo broken into 5 parts.  Feel free to view all 5 parts or simply view the ones that cover new territory.  Warning, brevity is not my strength since this demo could have been done in a few minutes :-)  It is best to watch the content in high definition video, of course.

Individual links here:

  1. Demo introduction and software download
  2. GlassFish Server installation and cluster setup
  3. Oracle iPlanet Web Server installation and setup
  4. Load Balancer Plugin Installation and setup
  5. Test Load Balancer & failover

Also, check out the blog post Kshitiz has written on the topic as well as the documentation.

Hope this helps!


Sunday Feb 27, 2011

GlassFish Server 3.1 - Full Java EE 6 Platform, Full Featured, Full Support

It's been over a year since GlassFish Server 3.0.1 was released as the first Java EE 6 compliant application server.  Today, GlassFish Server 3.1 continues to lead the way as the first Java EE 6 compliant application server with high availability clustering for both the full platform and the Web Profile.

Before getting into features, I'd like to thank the individuals that make up the extended product team for their amazing ability to execute.   Want the Java EE 6 Web Profile? Want the Java EE 6 full platform? Want a fully supported platform? Want some amazing developer features? Want some advanced production features?  They delivered.

From a product management perspective, we prioritized features that the community and customers wanted (and/or expected), and threw in a few good extras as well.  I'd like to thank the many community members that gave us feedback, filed bugs, etc.  Please keep the feedback coming.

UPDATE: Here are the download links:

This is also the first release where we split the documentation in two:

  1. The GlassFish Server Open Source Edition documentation (zip) covers the open source edition features.  The community should use this documentation.
  2. The Oracle GlassFish Server documentation covers the commercial product, including GlassFish Server Control features.  Commercial customers should use this documentation.  Features documented in commercial documentation are formally supported.

While I expect quite a bit of blogging today on various feature sets, I thought I'd highlight some GlassFish Server 3.1 "new features" here.  This is not even close to a complete list, but it's a start.

  • Provisioning.  GlassFish Server can now provision itself to remote hosts. Check out the "asadmin install-node" command.
  • Improved Clustering.   This is a no-brainer and pretty much what everyone has been waiting for.  Clustering in GlassFish Server 3.1 offers overall improved performance over GlassFish Server 2.1.1 (up to 34%), and smarter, faster failover. To our old friend the Node Agent: Rest In Peace.
  • Hybrid Java EE / OSGi applications.  OSGi services can rather seamlessly access Java EE components (like EJBs), and Java EE components can seamlessly inject OSGi services using the @OSGiService annotation
  • Application Versioning.   Deploy multiple version of an application, and roll backward or forward to another version. Thanks to Serli for contributing the feature.  I think the community will dig(g) it.  Check out the screencast.
  • Active Redeploy.  GlassFish Server 3.0.1 maintains HTTP session state when applications are redeployed.  This has now been extended to include Stateful EJBs.
  • Active Cache for GlassFish.  Coming in 1H 2011, Coherence\*Web becomes a drop-in replacement for in-memory HTTP session state replication. This enables much more flexible and scalable applications.  As a heads up, this will require an Oracle GlassFish Server license.
  • Embedded API.  We've done a lot of work on the embedded API, especially in the area of EJBs.  Also, our Maven support is outstanding IMHO.

We hope you enjoy this release, the first to support the supported full Java EE6  platform with clustering, high availability, and centralized administration.  If you go into production with this release, drop us a note and let us know.

Thursday Dec 10, 2009

GlassFish v3 - The First List of Firsts

Today we are releasing GlassFish v3 (community) and Sun GlassFish Enterprise Server v3 (commercial), following the release of Java EE 6 a few days ago.   Java EE is 10 years old - nearly to the day. GlassFish v3 - the project - is 4.5 years old (although the code base for GlassFish v3 is much older).

We've come a long way with GlassFish v3, and there are quite a few "firsts" in this release (correct me if I'm over zealous - I'm living on caffeine right now):

  • First Java EE 6 compatible community and commercial implementation
  • First Java EE 6 Web Profile compatible community and commercial implementation
  • First Java EE application server to start in seconds.
  • First GlassFish distribution under 30MB (GlassFish v3 Web Profile)
  • First time we managed requirements in the community
  • First time we realized a wiki is less than ideal for requirements management
  • First GlassFish release to document a public release schedule, milestones & all
  • First time we had to update the schedule in the wiki (due to Java EE 6 release change) :-)
  • First application server that exposes a RESTful management & monitoring API
  • First application server to let end users easily swap OSGi implementations
  • First application server to establish a community strictly around quality testing (survey metrics).   I simply cannot give this community enough kudos.  The breadth of test deployments really helped improve GlassFish v3 quality.
  • First application server to host dynamic language containers, such as JRuby and Jython. Web Archive packaging and servlet container not required. JRuby gem available.
  • First application server with a DTrace probe (ok, a bit aggressive since it will be in beta form due to JDK 7 dependency). Learn more (here) (here).
I'm not really done, but I have to get back to work. Feel free to comment on other "firsts".

Wednesday Aug 26, 2009

Developing a Web Application Using Java EE 6

Today, Harpreet and I delivered a webinar on "What's new with Java EE 6", and also covered a bit about GlassFish v3 as the reference implementation.  Wow, what a turnout.  In fact, the turnout was so large that we ran into some unfortunate issues that we'll definitely learn from.

First, we needed more panel members to answer Q&A (chat window), which was coming faster than we could answer.  In fact, I had problems with the highlighted question constantly losing focus, so I ended up answering the wrong chat question a couple of times. Apologies to attendees for not getting to more questions. 

Second, WebEx barfed on me when trying to share my desktop to thousands of attendees while trying to run a demo on writing a Java EE 6 version of the obligatory "Hello World" app with Servlet 3.0 and EJB 3.1.  The good news is that I whipped up a quick screencast of how to do this. Bear in mind it was done rather quickly, and if I had my druthers, I'd try to get it down a bit better.   However, you know people want to see a demo ASAP when they use the CAPS LOCK to say "CAN WE SEE THE DEMO?"   Without furthur ado, here goes the youtube (HD version here):


Monday Aug 17, 2009

GlassFish Tools Bundle For Eclipse 1.1 Released

It's official! GlassFish Tools Bundle For Eclipse 1.1 has been released and the bits are posted. Some highlighted features include:

  • OpenSolaris x86 support (Yeah!)
  • Eclipse IDE updated to 3.4.2
  • Pre-registered MySQL JDBC driver
  • SailFin v2 server target (download separately)
  • Added Maven Plugins
  • JAX-WS and JAX-RS runtime and Wizards added
  • Reduced download size due to Pack200 compression (~240MB, 160MB on Mac)

Note that Developer Expert Assistance is available.


Thursday Jul 23, 2009

Take the GlassFish Survey

If you have a few cycles to spare to help out the community, please take a GlassFish Survey to help the us all to better understand GlassFish adoption. It should take 5-10 minutes.

Centrally managing GlassFish Load Balancer configurations

Yesterday we delivered a webinar on setting up load balancing for GlassFish clusters: Make Applications Highly Available: Load Balancing GlassFish Clusters. I'll post a link to the replay when available.  The registration and attendance numbers were  pretty amazing, which tells me a couple of things:

  1. The community is either already using GlassFish Enterprise Server in production, or are considering to place it in production.
  2. The community would like to learn more about approaches to load balancing GlassFish deployments.

While GlassFish supports multiple load balancing approaches (hardware load balancers, mod_jk, and the GlassFish. We have been adding both marketing and engineering content in this area due to the amount of interest we are seeing (example).

One of the more interesting features of the GlassFish is the ability to automatically push out the load balancer configuration from the GlassFish Domain Administraton Console (DAS) to the GlassFish Load Balancer Plugin running in one or more remote web servers. Vivek demonstrated this feature during the webinar.  Because of time, we did not have to to demonstrate cluster setup/configuration or how to set up the secure communication channel between the plugin and the DAS.

First, you can set up a GlassFish high availability cluster, from download to validating the configuration, in under 10 minutes.  Of course, it takes a bit longer if you want to install a cluster across multiple hosts, but that's just boilerplate (s)ftp and time consuming.

To address the second point, setting up a secure communication channel, I thought I would double-click on that a bit and show you how to set it up. Again, this will be done on a single host, removing the boilerplate of FTPing the installer around.  The first step is to download the GlassFish Enterprise Server bits that include HADB (download url). This bundle also includes the load balancer plugin. Download the Sun GlassFish Enterprise Server v2.1 with HADB. I used the file-based installer during the demo instead of the package-based installer.

Side note - apologies for the webinar demo demons hitting the load balancer installation demo. For some reason the network was slow (GUI was updating too slowly), and the terminal was not refreshing properly, so I lost context of what screen I was on. Yes, I ran through the demo beforehand in the exact same way it was demo'd, 4 times without issues. Sigh.

Below is a script that will set up the secure connection between the DAS and the Sun Web Server to enable automated updates of the load balancer configuration. I've added documentation for each step.


#!/usr/bin/bash

#################################################################
# This script will set up the secure communication channel between
# the Sun Web Server and DAS for automated load balancer updates. It
# assumes that both the web server and DAS exist on the same
# box (hey, it's a DEMO ;-) )
#################################################################

#
# Top-level "HOME_DIRECTORY" variables. Examples are shown,
# replace variables with data that reflect your environment.
# Error checking of commands not shown :-/. Also note that
# in my demo, I put all bits under /var/tmp/demo directory.
#

WS_HOME=/var/tmp/demo/webserver7
JAVA_HOME=/usr/jdk/latest
DAS_DOMAIN=/var/tmp/demo/glassfish/domains/domain1

#
# Variables related to the web server configuration
#

WS_INSTANCE=https-my_webserver_instance.sun.com
SECURE_DAS_COMM_PORT=4443
LISTENER_NAME=http-listener-2

#
# Variables related to certificates. Because this is a demo, we will
# create a self-signed certificate.
#

CERT_NAME=ServerCert
CERT_ALIAS=s1as
CERT_EXPORT_FILE=/var/tmp/demo/etc/${CERT_ALIAS}.rfc

#
# Push any existing webserver configuration modifications, in case
# the load balancer was just installed in the webserver, for example
#

${WS_HOME}/bin/wadm \\
        deploy-config \\
        --user=admin \\
        --force ${WS_INSTANCE}

#
# Create a new HTTP listener to communicate with the GlassFish Domain
# Administration Server. This is the connection where the loadbalancer
# configuration changes will be pushed.
#

${WS_HOME}/bin/wadm \\
        create-http-listener \\
        --user=admin \\
        --server-name=${WS_INSTANCE} \\
        --default-virtual-server-name=${WS_INSTANCE} \\
        --listener-port=${SECURE_DAS_COMM_PORT} \\
        --config=${WS_INSTANCE} ${LISTENER_NAME}

#
# Create a self-signed certificate for demo or educational purposes. Typically
# a signed certificate will be installed for maximum security in production
#

${WS_HOME}/bin/wadm \\
        create-selfsigned-cert \\
        --user=admin \\
        --nickname=${CERT_NAME} \\
        --server-name=${WS_INSTANCE} \\
        --token=internal \\
        --config=${WS_INSTANCE}

#
# Set SSL property on the http listener used for DAS communication, using
# the certificate just defined
#
 
${WS_HOME}/bin/wadm \\
        set-ssl-prop \\
        --user=admin \\
        --http-listener=${LISTENER_NAME} \\
        --config=${WS_INSTANCE} \\
        enabled=true \\
        server-cert-nickname=${CERT_NAME}

#
# Export the DAS public key certificate stored in the Java keystore. Note that
# the Enterprise Profile (default for GlassFish w/HADB bundle) utilizes the
# NSS keystore, so this would be replaced with the equivalent certutil command.
#

${JAVA_HOME}/bin/keytool \\
        -export \\
        -rfc \\
        -alias ${CERT_ALIAS} \\
        -keystore ${DAS_DOMAIN}/config/keystore.jks \\
        -file ${CERT_EXPORT_FILE}

#
# Import the DAS public key certificate into the the certificate database,
# enabling a secure, trusted communication channel between the DAS and
# the web server.
#

${WS_HOME}/bin/certutil \\
        -A \\
        -a \\
        -n ${CERT_ALIAS} \\
        -t "TC" \\
        -i ${CERT_EXPORT_FILE} \\
        -d  ${WS_HOME}/admin-server/config-store/${WS_INSTANCE}/config/ 

#
# List the certificates in the web server certificate database
#

${WS_HOME}/bin/certutil \\
        -L \\
        -d ${WS_HOME}/admin-server/config-store/${WS_INSTANCE}/config 

#
# Push webserver configuration modifications to the instance
#

${WS_HOME}/bin/wadm \\
        deploy-config \\
        --user=admin \\
        --force ${WS_INSTANCE}



Wednesday Jun 03, 2009

GlassFish leads among Open Source adoption

We have been using multiple metrics, such as downloads and registrations, to measure GlassFish adoption, all of which you can check out at The Aquarium.  For example, GlassFish has been the most downloaded application server for quite some time, and is a leading indicator of what can happen further down the road.

Down that road, another metric is to measure the adoption of an open source project by other open source projects.  Because "open source" projects have source code publicly available, it is possible to automate the gathering of data/metadata for open source projects, which offers non-subjective evidence of adoption.  Ohloh (recently acquired by SourceForge) has been doing just that, by crawling 38,000 projects across 3,500 source forges. With the support of Ohloh, we have been able to measure the adoption of GlassFish within open source communities.

The results are in with this report, and GlassFish adoption has shown continued within open source communities.  In fact, the first graph shows that GlassFish is now the most targeted application server among open source projects, with over 50% of those projects supporting GlassFish.  The second graph (below) shows that new projects target GlassFish a stunning 73% of the time, far surpassing any other application server. Note that in both cases, projects can support more than one application server, hence the results total more than 100%.

The results of GlassFish adoption is apparent when you consider the growth in monetization of GlassFish. While Sun does not break out GlassFish Enterprise Server in our earnings reports, GlassFish is contributing to the growth of software infrastructure at Sun, and is a leading indicator that shows that the future opportunity looks bright for GlassFish Enterprise Server. 

 

Tuesday Mar 24, 2009

Introducing the GlassFish Tools Bundle for Eclipse

For me, it's Ground Zero for EclipseCon, 2009.  I wanted to get an early start to post about the GlassFish Tools Bundle for Eclipse, but it looks like Ludo beat me to the punch.  I was slowed down a bit by the fact that I forgot to pack toothpaste, which does not exactly mash well with booth duty. No worries, the hotel lobby personnel had my back, so my breath is minty fresh :-)

Sooooo, Sun is announcing the GlassFish Tools Bundle for Eclipse, which bundles community editions of GlassFish v2.1 and GlassFish v3 Prelude, Eclipse 3.4 (with Web Tools Platform), GlassFish Eclipse plugin and optionally JDK 1.6.  In addition, we've included the Java EE Javadocs, so you get Java EE API auto-completion.

Here are some notes about the bundle I think are worthwhile to mention:

  • The GlassFish Tools Bundle for Eclipse v0.9.9 is not quite FCS yet. Great quality, but we have a few motions to go through for a 1.0 release.  We're doing everything we can to get to 1.0 as quickly as possible.

  • The GlassFish Tools Bundle for Eclipse is \*extending\* the reach of GlassFish into the Eclipse community. In the past, developers had to pull together too many pieces (above) to get an Eclipse-based GlassFish environment.

  • To preempt the tinfoil hats, GlassFish will continue to ship with the award winning NetBeans IDE. In fact, check out this video Adam Bien's presentation at Community One East on the NetBeans 6.7 with GlassFish v3 Prelude. 3 slides and a ton of code.

  • If you are interested in using GlassFish with Eclipse, the GlassFish Tools Bundle for Eclipse is the quickest way to get there.  Eclipse is pre-configured (err, pre-integrated) with GlassFish, including log file viewing, http monitor, and more.

  • With GlassFish v3 Prelude, Eclipse developers don't lose HTTP session state when their application is re-deployed. Developer lifecycle simplified to edit-save-refresh browser. Keeps your mind on the problem, not the tool!

  • With GlassFish v3 Prelude, developers get an early look at Java EE 6 APIs, including JSF 2.0 Early Access and EJB 3.1 Lite Early Access (both in the Update Center).  JAX-RS is final and fully supported (also in Update Center).

  • The GlassFish Tools Bundle for Eclipse supports Windows, Linux, and Mac OS X. No worries, OpenSolaris is coming.
I'd say that's a good first-take introduction to the bundle. Time to head off to the booth!

Monday Mar 16, 2009

Update that blog pic!

I do like to see bloggers post a pic of themselves on their blog. Just in case I run into one of 'em at a trade show.  However, I've always been bugged at personal portrait pictures on blogs, articles, etc that are waaayy out-of-date. I swear that PR folks never updated the Scott McNealy pic during his tenure as CEO. To each his own, I suppose.

The pic I had on my blog was about 6 years old, which made me a target of my own criticism. I kinda liked that pic, though. Fresh hair cut. 165lbs. 36 yrs young.  No signs of bald spot.

Today I decided to update the pic. What a difference 6 years makes!  42 years old. Less hair to cut (barring nose/ears). 20lbs heavier. A newly forming bald spot is racing my receding hairline to the top of my head (my money's on the bald spot). I'd swear my nose is 2mm (.005%) longer. I could go on. And on. And on.  However, it's me. Uncut and raw. The real deal. Dagnabit, I'm diggin' it.

I've been thinking about updating the pic for a while, when I finally saw one that made the grade.  A bit too "visionary-looking" for my taste, but the alternatives weren't as promising - such as me in Las Vegas with a ... (never mind) or at the beach without a shirt (Vegas pic is way better).

Stay tuned for 2015.

Tuesday Feb 10, 2009

GlassFish Production Deployments & Enterprise Manager

Busy, busy day. Lots of news regarding Sun GlassFish Portfolio in general, and  Enterprise Manager in particular. I will in no way try to keep up with Nazrul on Enterprise Manager blogging :-)

I have spoken with countless customers about GlassFish Enterprise Server over the last 18 months (such as T-Mobile and TravelMuse), and it's no surprise common threads appear, such as cost reduction, avoiding vendor lock-in, and support for the latest standards (sooner). The concerns customers have with products based on open source center primarily around support and the ability to troubleshoot production issues.

Regarding support, GlassFish Enterprise Server subscribers have access to 24x7 support with live call transfer for high priority ("production down";) issues. In addition, Platinum support offers a Customer Advocate who understands customer deployments, resulting in faster problem resolution and escalation management. However, a Customer Advocate also acts in a proactive manner via regular meetings to keep up with customer environments and issues, and can work with customers on practices to avoid downtime.

To address concerns with visibility into production deployments from a product perspective, Sun is  introducing Enterprise Manager with GlassFish Enterprise Server v2.1 (and GlassFish Portfolio). I'll reiterate Nazrul's coverage of Enterprise Manager, which is a good one-stop shop that covers the improved manageability and observability features.  Of particular importance is the ability to avoid downtime in the first place with various alerts and log file management.  We expect many enterprise customers will have enterprise management tools in place. For these customers, SNMP monitoring support is key. A really helpful feature that is generally JDBC pool management.  JDBC pool management is essentially "auto pilot" for JDBC connection pool optimization. Turn it on and, odds are, you will get better performance with less overhead.

If you get a chance, check out Nazrul's Enterprise Manager post and feel free to give us feedback. We look forward to it!


Monday Feb 09, 2009

GlassFish Contribution to Sun Software Infrastructure Growth

In case you haven't viewed the Q2FY09 quarterly earnings announcement, both MySQL/Infrastructure software and Niagara-based servers are growing strong. Sun doesn't break down the numbers to specific products, but the revenue shows that a growing number of customers are coming to Sun as they build out their web infrastructure.


FY08
Y/Y Growth

Q1FY09
Y/YGrowth

Q2FY09
Y/Y Growth

 CMT Servers
84%
83%
31%
 MySQL / Infrastructure
5%
111%

55%

As for GlassFish, I go home each day with a smile on my face knowing that GlassFish Enterprise Server is contributing to that growth with many new customers.  Calendar year 2008 delivered roughly 9 million downloads, and over 300,000 registrations. Registration is optional, so we do our best to earn it. Feel free to use the GeoMap to view the growth. While I am continually and pleasantly surprised by these numbers, I can't help but feel we are only getting warmed up as our virtual team - both Sun and non-Sun - continues to grow.

All this being said, we are not resting on our laurels. Nope. Too much on our plate in order to continue earning new customers. We're listening.  What do you like about GlassFish/Sun/community? How can we improve GlassFish/Sun/community?  Feel free to contact me directly, or use the GlassFish user's email alias to provide feedback. Other routes to feedback include the The Aquarium blog, FishCAT (GlassFish Quality community), GlassFish.TVTwitter, and the plethora of GlassFish community bloggers (too many to list).

Tuesday Jan 13, 2009

GlassFish High Availability Recap

Two recent high availability mediacasts, the GlassFish Clustering screencast and the recent GlassFish High Availability webinar (and companion whitepaper), have done well (IMHO).   To quickly summarize, the screencast covered download, setup, and validation of a GlassFish cluster. The webinar covered architectural approaches to deploying GlassFish clusters in a virtualized environment.

The screencast hit > 1,500 views in total (YouTube + Sun Learning Exchange). Time well spent on my part, I think. Hopefully it was time well spent on the viewers part as well.

As for the webinar, over 1,000 registered to attend the webinar, hundreds attended, and hundreds are viewing the replay. Lots of questions occurred during the chat, and some business relationships were formed in the process.

Me-thinks we've addressed a bit of pent-up demand on GlassFish High Availability.

Wednesday Dec 24, 2008

Reflecting on GlassFish in 2008

Sssooo many things have happened with GlassFish in 2008, I was a bit hesitant to write this blog in fear of missing something.  Then again, I'm not known for being a shy blogger. These are not in an order of importance or priority, just rolling off the top of my head in my "brevity is not an option" blogging style.

  1. Adoption. GlassFish adoption is through the roof. Were still counting, but somewhere near 9 million downloads and 300,000 product registrations. Exceeded my expectations. That's more than one download for every Java developer!? Me-thinks that developers are trying to stay current with latest versions.  Feel free to track GlassFish adoption using the GeoMap or on The Aquarium.

  2. JRuby on GlassFish. Quite popular thanks to the work by Jacob, Arun, Vivek, Charles, Thomas, and others. No doubt this is contributing to GlassFish adoption. GlassFish in the twittesphere and the blogosphere quite active.

  3. Customers.  Quite a bit of commercial interest in open source in general and GlassFish in particular.  Customers like the innovation and transparency, not to mention the flexibility of "paying at the point of value" that open source enables. Follow our growing list of customers here and here.

  4. GlassFish Performance. It's an understatement to say that GlassFish performs well. It is hands-down the fastest open source application server. I've seen many customer benchmarks comparing GlassFish to closed source application servers, and GlassFish has either met or exceeded the competition. When price is thrown into the equation, customers begin to ask themselves "Why am I currently paying up to $50K/CPU for my closed source application server?"

  5. FishCat launched. Proof that open source innovation does not have to be limited to lines of code. Check out the contributor list that are constantly improving GlassFish quality.

  6. GlassFish v3 Prelude.  For early adopters, this is a fully QA'd and supported release of GlassFish layered on an OSGi mickrokernel, with some nifty developer productivity features. While this release has a slightly different feature set than GlassFish v2, it'll eventually be a superset of Glassfish v2.

  7. GlassFish on UStream. Eduardo launched an ongoing series of interactive community sessions on various topics, by both Sun and non-Sun community members. Active Q&A.

  8. GlassFish Updates. While originally targeted for January 2008, GlassFish v2 UR1 was actually released \*early\* and pulled in to December 2007. Mid-2008 we released GlassFish v2 UR2 with bug fixes and performance enhancements. GlassFish v2.1 isn't far around the corner with additional bug fixes and performance improvements.

  9. OpenMQ Updates. OpenMQ has been cruising along with it's latest 4.3 update. Highly peformant. Scalable (\*really\* scalable). Highly available. Bundled with GlassFish.

  10. GlassFish ESB released. GlassFish ESB is Open ESB in commercial form. Supported. Feature rich. Java Business Integration support at its core.  Layers right on top of GlassFish. NetBeans Integration. Learn More.
I'll cap it off at 10 for now. Feel free to add to this list.
About

John Clingan

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today