Supercomputing and Linux

via 451 CAOS Theory

I haven’t realized yet how far Linux extremely dominates the Supercomputing market as Operating System.

Evolution of the Linux OS share in the Top500 (Supercomputing 2009):

  • November 2007: 84.6%
  • November 2007: 87.8%
  • November 2009: 89.2%

All Top10 systems are based on Linux.

The 451 Group published also another “worth-to-read” article about Open source software and the need for speed.

We’ve also seen speed as a factor for building and providing cloud computing infrastructure. Vendors report that Linux is ideal for cloud construction since the availability of source code means that unecessary pieces can be relatively easily and quickly cut out of the OS.

BY the way, more than 80% of the Top500 systems are using Intel computers, 10% IBM Power processors, and 8% AMD Opteron. More than 85% are already based on Quad-core processors! HP is delivering 42% of the servers, and IBM 37% (source: Top500 computer sites).

And: 82% of the Top500 systems integrate between 2’000 and 8’000 processors. 1% more than 128’000 processors (source: Top500 computer sites)!

And: the Top1 (a Lab of the US Department of Energy) uses 224’162 AMD Opteron Six Core 2.6 GHz processors and generates 1’759 TFlops (source: Top500 computer sites).

MVVM Light Toolkit V2

via Laurent and the Innoveo Blog

Cool stuff!

At Innoveo Solutions we are using .NET and WPF for our Innoveo Skye® Editor application. Skye® Editor is a distribution channel editor targeting business people letting them edit and configure their insurance products.

From the beginning we have adopted the Model-View-ViewModel architecture. Having our solution growing we were facing the issue of having our ViewModels dependency growing too. Some ViewModel became too much dependent of others. This was obvious in our unit tests whose complexity to setup were growing too. It was time to find a solution to decouple the ViewModels.

The solution came out after a discussion with Laurent Bugnion, the famous author of MVVM Light Toolkit. At that time we used the V1 that already helped a lot in this decoupling.

Now with MVVM Light Toolkit V2 it is even better with the new Messenger API. What we also really appreciated in comparison to other frameworks is that it is really light and the ability to open and edit the user interface into Expression Blend.

So Thank you Laurent for this GREAT framework and I looking forward for V3!

I also would like to thank my managers at Innoveo Solutions who understand Open Source and the need to have people contributing to Open Source projects, even during their professional working time. A Win-Win situation and not just a one way benefit as often.

Thanks also from my side to Laurent Bugnion, great work and contribution!

VMware/SpringSource – About PaaS

VMware announced on August 10, 2009 its willingness to acquire SpringSource for $362 million in cash and equity, plus $58 million of unvested stock and options (press release). The process should be closed in Q3 2009.

How can this acquisition be interpreted? What are the goals of VMware/SpringSource?

Some interesting inputs and analysis found on Internet.

A post from Rod Johnson, CEO of SpringSource

About the merge itself

[…] We have signed a definitive agreement with VMware, who will acquire SpringSource. Subject to regulatory approval, we expect the transaction to close in Q3. SpringSource will become a division within VMware. I will continue to lead SpringSource, reporting to VMware CEO Paul Maritz.

About the opportunity

[…] But the broader transformation in IT goes beyond Java frameworks, tooling and runtime infrastructure. The way in which people think about software stacks is changing. Virtualization is reshaping the data center, and cloud computing is set to drive far-reaching changes. Significantly, cloud computing blurs the division between development and operations, bringing new power (and responsibility) to developer.

And so the question becomes, what is the most simple, powerful, pragmatic way of utilizing SpringSource technologies in the data center, and in the cloud?

About the vision

Working together with VMware we plan on creating a single, integrated, build-run-manage solution for the data center, private clouds, and public clouds. A solution that exploits knowledge of the application structure, and collaboration with middleware and management components, to ensure optimal efficiency and resiliency of the supporting virtual environment at deployment time and during runtime. A solution that will deliver a Platform as a Service (Paas) […]

About the vision (said in other words)

The next chapter of our work at SpringSource is tackling those challenges: Building on our Build/Run/Manage solution to provide the industry’s best solution from developer desktop to cloud deployment. Bringing Spring’s power and simplicity to enabling the millions of Java developers to benefit from the full power of cloud computing. […]

About the representation of this vision

SpringSource Build/Run/Manage and VMware Cloud

About the open source community

Our commitment to open source practices, licenses and traditions will remain unchanged. We expect our contributions to open source to increase. Our open source projects will retain their commitment to enabling user choice. Spring will retain the portability between deployment environments that empowers users. […]

An analysis from 451 CAOS Theory

Part I

[…] VMware is clearly in need of a story beyond virtualization, even if we are still relatively early on in enterprise adoption. Still, looking into the future, it sees clear skies, and that does not fit with the multi-billion dollar opportunity shaping up in cloud computing. Thus, VMware is willing to invest a significant amount in SpringSource, which does represent a crossover in customers without much, if any, crossover in competition.

Part II

VMware is working to address its increasing competition from all sides. While it may seem somewhat odd for VMware to want to get involved in enterprise Java application development and deployment, it may want to take advantage of SpringSource’s relatively quick climb in the enterprise Java development and support business. VMware may also be looking to offset any gain in enterprise Java influence and control by Oracle, which may do so with its more than $7 billion acquisition of Sun Microsystems.

Part III

VMware is also facing increasing competition from OS vendors, including Microsoft, Novell and Red Hat, which is among SpringSource’s biggest competitors with its JBoss business. Again, SpringSource may not seem the most likely suitor for Java application development, but VMware may see this as an area where it can most effectively integrate its own technology and talent to differentiate in virtualization and cloud computing.[…]

Open source?

Although SpringSource’s open source nature has been critical to its developer reach and success, this is likely not as important to VMware, which may view SpringSource more as a subscription software company than as an open source software company. Either way, it seems VMware, similar to Oracle, may have somewhat limited vision when it comes to open source software, seeing it for its development and time-to-market advantages, but missing other community benefits — including user and customer communities, feedback and contributions — that help make things work.[…]

Disclosure: Innoveo Solutions is using Spring in its Innoveo Skye™ software product.

cross-posted on the Innoveo blog.

Cédric nominated to the EOS Directory Advisory Board

I am very proud to announce that Cédric Walter, one of our colleague and founding member of Innoveo, is nominated to the EOS Directory (Enterprise Open Source Directory) Advisory and Expert Board. Cédric is a very well-known contributor of the Joomla community since 2004.

EOS Directory is a great catalog of more than 350 open source projects, that are listed, described and analyzed. It is today the leading online platform to help enterprises and organizations identify and evaluate Open Source technologies. Initially launched by Optaros, about two years ago, the platform has been recently handed over by Bruno von Rotz, initial sponsor of the initiative, well known Open Source specialist, and one of our Innoveo Board Member.

In support to strengthen the neutral approach to ratings and selection of the technologies, the new EOS Directory Advisory and Expert Board has been established over the last weeks.

The Advisory and Expert Board will be both instrumental in guiding the future development of the EOS Directory Platform as well as in making sure that the content is accurate, relevant and fairly represented. (Source: EOS Directory Blog)

Congratulations to Cédric!

More Information on Cédric’s blog and the EOS Directory blog.

Cross-posted on the Innoveo Blog.

Software maintenance

via Judith Hurwitz

Judith is bringing, as usual, interesting feeds for thoughts, this time in the field of software maintenance fees.

[…] As the world slowly moves to cloud computing for economic reasons there will be a major impact on how companies pay for software. Salesforce.com has indeed proven that companies are willing to trust their sales and customer data to a Software as a Service vendor. These customers are also willing to pay per user or per company yearly fees to rent software. Does this mean that they are no longer paying maintance fees? My answer would be no. It is all about accounting and economics. Clearly, Salesforce.com spends a lot of money adding functionality to its application and someone pays for that. So, what part of that monthly or yearly per user fee is allocated to maintaining the application? Who knows? And I am sure that it is not one of those statistics that Salesforce.com or any other Software as a Service or any Platform as a Service vendor is going to publish. Why? Because these companies don’t think of themselves as traditional software companies. They don’t expect that anyone will ever own a copy of their code.

The bottom line is that software will never be good enough to never need maintenance. Software vendors — whether they sell perpetual licenses or Software as a Service– will continue to charge for maintance. The reality is that the concrete idea of the maintenance fee will evolve over time. Customers will pay it but they probably won’t see it on their bills. Nevertheless, the impact on traditional software companies will be dramatic over time and a lot of these companies will have to rethink their strategies. Many software companies have become increasingly dependent on maintenance revenue to keep revenue growing. I think that Marc Benioff has started a conversation that will spark a debate that could have wide ranging implications for the future of not only maintenance but of what we think of as software.

Interesting!

Cross-posted on the Innoveo Blog.

Oracle buys Sun

via Between the Lines

As everybody already knows, Oracle is buying Sun for about $7.4 billion, including Sun’s debt ($9.50 a share in cash). Some interesting thoughts from Larry Dignan, Editor in Chief of ZDNet.

  • [Oracle] added that the acquisition of Java “is the most important software Oracle has ever acquired.”
  • Oracle also becomes a full-fledged hardware player.
  • Oracle and Sun have been long-time partners. […] “More Oracle databases run on the Solaris Sparc than any other system,” said Ellison, noting Linux was second. “We’ll engineer the Oracle database and Solaris operating system together. With Sun we can make all components of the IT stack integrated and work well.”
  • Oracle with Sun appears to be the Apple of the enterprise. Indeed, Oracle President Charles Phillips noted that the company is looking to offer everything from apps to the disk.
  • Oracle’s stack of IT stuff now includes:
    • Java;
    • Solaris;
    • Enterprise applications ranging from CRM to ERP to business intelligence;
    • The database (Oracle and MySQL);
    • The middleware;
    • The storage hardware;
    • Cloud computing services;
    • And servers.
  • Art of War approach:
    • Oracle gets to annoy IBM—and own Java—over a few pennies a share more than Big Blue was willing to pay.
    • Oracle gets to kill MySQL. There’s no way Ellison will let that open source database mess with the margins of his database. MySQL at best will wither from neglect. In any case, MySQL is MyToast.
    • Sun has a big installed base. All the better to upsell applications into.
  • Sun was relatively cheap compared to Oracle’s other acquisitions. The price was above the Hyperion buyout but below PeopleSoft and Siebel.
  • Oracle saves Sun management from what could have been a complete debacle following the IBM takeover talks. The Sun board had been split on the IBM deal. Today, it’s all roses.

The official Oracle press release can be found here.

It is clear that this deal will change the IT landscape quite massively. And the consolidation is definitely not finished…

Cross-posted on the Innoveo Blog.

Twhirl v0.9 is out!

The new version of Twhirl is out after a good organized and dynamic private beta phase. You can download it here.

This version is very stable, no problem to attend on this side.

I’m quite a fan for a while of Twhirl as a Twitter client. Now, it allows also to broadcast your messages to Twitter, Flickr, LinkedIn, Facebook, etc. through the ping.fm service.

By the way, do you know this ping.fm service? Really great! It allows to publish centrally and to push your messages to the different “status” services of the main social networking websites. Worth a try, it’s free!

twhirl

Below, some information about Twhirl.

Twhirl features

  • multiple Twitter, laconica, Friendfeed and Seesmic account support
  • runs on Windows and Mac OSX (and Linux)
  • notifications of new messages across all of your accounts
  • shorten long urls easily (using snurl, twurl or isgd)
  • post images to TwitPic
  • search tweets using Twitter Search and Tweetscan
  • timeline filtering
  • groovy color schemes to personalize your experience
  • automatically checks for new versions

What’s new in Twhirl v0.9

  • spellchecker (currently English only, can be deactivated in settings if you use Twhirl in other languages)
  • your Twitter @replies will display even if you are mentioned in the middle of a tweet – don’t miss anyone quoting your name
  • share all your updates to all your favorite social software via Ping.FM support: Twhirl now posts to Facebook, MySpace, LinkedIn and more
  • follow any topic in near-realtime: searching for a term or a brand and then activating it as a saved search it will bring all future mentions of it into your timeline
  • record a video and post it straight to Twitter, then get your Seesmic video replies and follow the video conversation
  • get new Seesmic replies and videos in realtime thanks to XMPP support
  • support for bitly url shortnener with stats and history
  • support for direct messages and favorites on laconica/identica

Actually, I’m using Twhirl as micro-blogging client, without being a seesmic user ;-)

Have a look also at the video from Loic, showing how Twhirl is working.

Marten Mickos, former MySQL CEO, is to depart Sun

via 451 CAOS Theory

It seems that SUN will not communicate on that, but Marten Mickos, the former MySql CEO, is leaving SUN, after about 1 year… I remember one of my post in February 2008 with some explanations about the “why” of this merge, directly from Marten. Outch. Something didn’t work as planed there.

Some more information below.

I just got news that Marten Mickos, former MySQL CEO, is to depart Sun amid a reorganisation of its infrastructure and database business units. Don’t expect an announcement from Sun on this, but the news is confirmed.

[…] Marten will be transitioning out of Sun by the end of the company’s (current) third quarter.

Marten’s departure is a big loss for Sun and follows quickly after the departures of Monty Widenius and David Axmark.

[…] Matt Asay is right, Marten’s departure “is likely to lead to an exodus among MySQL’s deep talent pool”. This needn’t be a complete disaster – the same thing happened at JBoss and Red Hat has recovered from that, but this is going to be a serious test for Sun’s ability to maximize on the potential of MySQL and its other open source assets.

Matt also writes that “Mickos was the backbone of MySQL’s rising revenues, as an open-source pragmatist and visionary. He was the face of MySQL, but also of the rising open-source industry.” This is true, and for that reason I hope it’s not too long before we see him taking charge at another vendor.

Good luck to Marten, hope to see him asap in a new role!

Comparison of Open Source Application Servers

openlogic

I have found – by accident really! – a very interesting presentation on SlideShare concerning the different leading Open Source Application Servers on the market.

This very solid evaluation is proposed by OpenLogic.

I have summarized parts of it below.

Goal of the presentation /

Help you choose which open source application servers to evaluate more thoroughly:

  • JBoss
  • GlassFish
  • dm Server
  • Geronimo
  • Tomcat

Which open source application servers are your using or considering using /

appserver

J2EE Didn’t Fill the Need /

  • EJB 2 is difficult to use
    • Many people consider it unnecessary difficult
    • Entity Beans were especially problematic
    • But even session beans earned bad reputations
  • The Open Source community responds
    • OSS packages mitigating the problem
      • Hibernate instead of Entity Beans
      • Spring as a component model
    • They were very successful in the marketplace
  • Many Spring/Hibernate applications
    • Required only Tomcat to run but also work in full app servers

When Tomcat Is Not Enough /

  • Tomcat doesn’t support
    • JMS
    • EJBs
    • Other…
  • Enterprises need integration
    • The more mature the app is, the more likely it is to be added
  • Add-ons
    • It was possible to add things that Tomcat was missing
    • But this became a “build your own Frankenstein” exercise

Java Enterprise Edition in the Meantime /

  • Weaknesses in EJB 2 model were recognized
  • Work on new specification was completed
    • J2EE → JEE 5
    • EJB 2 → EJB 3
      • Entity Beans → JPA
  • EJB 3
    • Simple annotation-based programming model
    • Not everybody adopted EJB 3
  • JEE 6 will embrace modularity
    • Profiles, including web profile

Choices in 2007 /

  • Use Spring
    • Start with full app server
    • Start with Tomcat, build from there
  • Use EJB 3
    • Requires full app servers
  • Full application server
    • Pros – everything you are likely to need, could use EJB
    • Cons – complexity, might use more resources then Tomcat
  • Tomcat
    • Pros – small, simple, low resource usage
    • Cons – you might need to build your own app server, no EJB

OSGi /

  • Started in 1999
    • Recently got a lot of exposure
    • In particular, R 4.1
      • JSR-294
  • OSGi brings
    • Dependency management and modularity
    • Ability to load only parts it needs
  • OSGi currently has a lot of mindshare

The central questions /

  • Decisions, decisions
    • EJB 3 or Spring
    • Spring on dm Server or on J2EE/JEE server?
    • OSGi or not OSGi
    • Do I need EJB 2 compatibility?
    • In addition, there are many “old” considerations
  • Servers are not “all inclusive”
    • EJB 3 apps won’t work on SpringSource dm Server or Tomcat

Assessment JBoss /

JBoss Thought Leadership

  • Complete ecosystem
    • Portal
    • ESB
    • BPM
  • JBoss has history of innovation
    • Pioneer of EJB 3
    • Seam Application Framework
    • Web Beans
  • OSGi
    • Support in JBoss 5

JBoss for Developers

  • Excellent customizability
    • JMX-based, don’t deploy what you don’t need
  • Seam is worth a look for developers
  • JDK 6 with 4.2.3 and 5.0 GA
    • JDK 5 compiled binaries work on both JDK 5 and JDK 6
  • JBoss IDE
    • Eclipse-based
    • JBoss Tools
      • Free version (RHDS is paid version)

JBoss in Production

  • Dependability
    • Excellent clustering and failover capability
    • Reliable in production
  • Monitoring and deployment capabilities
    • Not really oriented toward system administration out of the box
      • Command line/file edit flavor of configuration
      • GUI tools (Tomcat manager and JMX Console) are fairly basic
    • Excellent 3rd party tools available for monitoring
      • Hyperic
      • GroundWork IT
      • JON *

JBoss – Conclusions

  • Strengths
    • Mature, scalable and reliable
    • Good support for J2EE and EJB 3
    • Seam framework
  • Weaknesses
    • Limited GUI-based configuration in open source version
    • LGPL License may be a concern for ISV’s embedding app servers

Assessment SpringSource dm Server /

SpringSource dm Server

  • Newcomer
    • Released in April of 2008
    • GPL license
    • Incorporates many mature components
      • Spring Framework
      • Tomcat
      • Equinox
    • dm Server users are very early adopters
  • Different take on app server
    • OSGi support
    • No support for EJB
    • No JMS out of the box

dm Server for Developers

  • Server works well with Spring Framework
  • IDE
    • Spring IDE – IDE for Eclipse platform
    • Support for NetBeans and IntelliJ
  • OSGi support
    • Resolves “dependency hell”
    • But requires application migration to take advantage of it
  • Supports Java 5 and 6

dm Server Thought Leadership

  • OSGi-based
    • Good OSGi implementation
    • OSGi discussed a lot in their documentation
  • No support for EJB
    • No support for EJB 3 or old EJB 2 spec
  • Spring offers similar functionality to Seam
    • Which is somewhat more mature
    • Although some of the Seam ideas might be somewhat more powerful
      • Bijection

dm Server – Conclusions

  • Strengths
    • Support for Spring Framework
    • Support for OSGi
  • Weaknesses
    • Newcomer
    • No EJB
    • Limited experience among workforce

Assessment Tomcat /

Tomcat

  • First release (3.0.x) in 1999
    • Apache license
  • Servlet container
    • Lightweight server
  • Used in many other app servers
    • JBoss
    • dm Server
    • Geronimo

Tomcat – Conclusions

  • Strengths
    • Lightweight
    • Well known and tested
    • < li>Fast startup/deployment for development

  • Weaknesses
    • No support for EJB, JMS or almost anything else outside of “web side”
  • Tomcat in Development and Production

    • Tomcat 6 supports
      • Clustering
      • Failover
    • Widely used for both development and production
    • Supported in most popular IDEs

    Conclusions /

    • App servers are not just about the JEE specs
    • Make some high-level decisions before evaluation
      • Do I need EJB 2 compatibility?
      • Do I intend to follow EJB 3 and other industry standards?
      • Do I need something fast, lightweight, and easy to use?
      • Do I have a need for lifecycle management of server components (through OSGi)?
      • Do I need support for dynamic languages like Groovy and JRuby?
      • Am I an early adopter of new technology?

    Recommendations /

    • “I’m using EJBs and I’m conservative”
      • JBoss, GlassFish
    • “I don’t need XA/JMS/EJB”
      • Tomcat, JBoss, GlassFish, dm Server
    • “I’m using Spring”
      • Conservative – JBoss, Tomcat, GlassFish
      • Leading edge – dm Server
    • “I need to embed an app server in my commercial code”
      • Tomcat, Geronimo
    • “I use Spring heavily and I need OSGi”
      • I need it today and don’t need EJBs – dm Server
      • I need it soon and/or need EJBs – GlassFish, JBoss
    • “I use Seam”
      • JBoss
    • “I want ActiveMQ/Spring/Hibernate preinstalled”
      • Geronimo
    • “I need dynamic language support”
      • Groovy/Grails – dm Server, JBoss, GlassFish
      • JRuby/Rails – GlassFish, Geronimo

    Firefox Add-on – ScrapBook

    I am not using so many Firefox Add-ons but this one – ScrapBook – is just great!

    You can download it here.

    What is ScrapBook

    ScrapBook is a Firefox extension, which helps you to save Web pages and manage the collection. Key features are lightness, speed, accuracy and multi-language support.

    Functionalities

    Major features are:

    Good tutorial here (pdf, 692KB)

    Screenshot

     

    scrapbook