Monday Apr 18, 2011

GlassFish Geo Map Updated - Mar 2011

One of the multiple ways GlassFish adoption is tracked is by doing a reverse geo-lookup on the IPs from the GlassFish Admin Console and plotting them on a Google Map. The data is not very precise as not everybody uses the web-based console and proxies and firewalls get in the way but this is an interesting visual representation. You can zoom in/out and the numbers for the visible area are updated on the right bar.

The bottom left corner allows you to view the monthly or the cumulative total. The "IP" labels represent installations and "hits" count repeated GETs.

A live version of map can always be seen at maps.glassfish.org and a snapshot from Mar 2011 is shown below:

The world is certainly becoming pink :-)

This data has been gathered since Feb 2007 and has > 21 million hits from ~1.2million unique IPs through Mar 2011. The data for Mar 2011 is the highest so far: 691k hits from 48k unique IPs. This can certainly be attributed to the GlassFish 3.1 launch in the late February.

Do you know there are GlassFIsh users in Greenland as well ? I'm still waiting for research stations in Antartica to use it :-)

Go ahead, take a look at the live version and see who is using GlassFish in your neighborhood! Drop a comment on this blog if your city is shown in pink color.

Technorati: glassfish adoption geomap google mashup

Wednesday Jul 30, 2008

Why GlassFish Metro over Axis ?


Metro (Web services stack from GlassFish) is kicking strong these days - here are two instances!
  1. ArcGIS SOAP stack gains 90% performance improvement using Metro

    An intern in the Web services team for performance enhancement of ArcGIS SOAP SDK reported:

    "With Axis 1.x based tool kits XML parsing was identified as a bottleneck and therefore we wanted to make a switch to a tool kit that uses the Streaming API for XML Parsing (StAX). We identified that Metro (Glassfish's SOAP Stack) was the way to go and i generated the new Metro based SDK for accessing Web-Services."

    And the conclusion is ...

    "The result of this project is an increased performance of the ArcGIS Server's SOAP stack (by about 90%)."

    Pretty cool - Metro (Web services stack baked in GlassFish) gave about 90% improvement over Axis! Read more details about the study here.
  2. Change of the guard: AXIS out, JAX-WS in

    Here are some relevant points:

    "I have come to a conclusion: I no longer want to deal with the hassle that has become Apache AXIS."

    "AXIS2 is current, but has become very large, the doc is poor, the support is invisible, the generated code smells, and the seams are everywhere.  Fifty nine jar files?  Really?   Do I need this hassle?  With JAX-WS, do I need AXIS any longer? I think not."

    "But I honestly cannot believe customers will continue to put up with the furball that AXIS2 has become. And if I am in a position to make a recommendation, I will recommend JAX-WS. It works."
And you can also connect to Microsoft Exchange Server using JAX-WS.

And here are some other endorsements for Metro.

Technorati: webservices adoption glassfish metro axis
About

profile image
Arun Gupta is a technology enthusiast, a passionate runner, author, and a community guy who works for Oracle Corp.


Java EE 7 Samples

Stay Connected

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