Tuesday Apr 28, 2009

Which Application Server to use with MySQL?

At the MySQL User Conference last week I had a number of attendees come up to me to ask which application server they should be using with MySQL. They were looking for something that was fast, lightweight and compatible. To me the choice was obvious -- GlassFish

So why GlassFish?

Project GlassFish, was launched when Sun open-sourced its application server and the Java EE Reference Implementation, was Sun's first step toward open-sourcing the entire Java platform. Less than a year after the initial launch, the GlassFish community delivered the first release of the GlassFish Application Server, a production-quality, Java EE-compliant application server, followed by a second release in 2007. Today, GlassFish is the leading open-source and open community platform for building and deploying next-generation applications and services. The GlassFish application server has been downloaded more than 18 million times since 2006.

Another choice might be Red Hat's JBoss application server that was released in 2006. Although JBoss has had some success in the past, I would caution that there are some issues around  backward compatibility and features that are not supported in the commercial release of the product. In addition it seems to be pretty far behind as far as latest features around JavaEE are concerned.

In contrast, the GlassFish application server is backward-compatible; features released today will be supported in future freely available versions as well as future Sun-supported commercial versions of GlassFish Enterprise Server. Additionally, the freely available GlassFish application server is ready for production right out of the box. For these reasons, I recommend GlassFish application server over JBoss!

Tomcat application server is extremely popular with Java developers who only want to only use servlets, but it doesn't support the full Java EE stack. So why use only a bit of Java when you can use the full reference implementation?

Wednesday Jul 23, 2008

What is LAMP?

We have been having a lot of interesting internal debates about what to call our new offering in the LAMP space -- see release: Sun Microsystems Unveils Enterprise AMP Stack.

As we all know LAMP started off as being (Linux, Apache, MySQL, and PHP) but if I use Ruby am I suddenly not a LAMP developer am I a LAMR developer? Or if I use Apache, MySQL and PHP on Windows, am I a WAMP developer? And what do I call it if I use Progress, or Python, or ?

Internally we often call our Solaris stack SAMP, but again it just seems strange that for each variant we have another 4 letter acronym.

So what should we have called our offering?  Basically we are supporting Apache, MySQL and PHP on Linux, Solaris and Windows.


Friday Jun 27, 2008

How to save $2.76 Million USD

We have been working really hard at creating a compelling offering for customers that want to be freed from proprietary database and application server vendors that are arbitrarily raising their prices. We have just announced a New GlassFish and MySQL Offering that gives unlimited usage based on the number of employees in an organization. If you have not heard the news listen to a recap here, or read the full press release here.

For a typical customer with under 1,000 employees running application servers on 20 dual-CPU, dual-core x86 servers and running database servers on 10 dual-CPU, dual-core x86 servers, the three year total cost of ownership (TCO) for proprietary software will exceed $3 million USD. The three year TCO for GlassFish and MySQL Unlimited for this same configuration is just $240,000 USD – a savings of over $2.76 million USD. For details on the comparison see http://www.sun.com/mysql/glassfish

At last a solution that doesn't require you call your software vendor if you decide to add database instances, or deploy on more machines, or change hardware configuration, or ...

Check out the site and let me know how much your company will save.


Musings from Mark Herring at Sun...


« February 2016