Innoveo is a member of the Oracle PartnerNetwork

oracle[1] Innoveo Solutions enjoys its new membership to the Oracle PartnerNetwork, which is illustrating the long and successful deployment of our insurance frontend solution – Innoveo Skye® integrating Oracle databases.

Our partnership with Oracle helps us to leverage our expertise and build on the strong foundation that Oracle’s technology provides.

Innoveo news.

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.

Mark this day :-)

Yesterday (Thursday) was an absolutely important and central milestone in the life of our company – Innoveo.

I am very proud, totally exciting for the coming steps, exhausted, and also in a way – relieved. First confirmations that our vision, strategy, and tactics are not sooo bad ;-)

As usual, a bit of luck, plus a great help and support from very smart people (hello René), and from our Team!

I remember a thought of one of my former boss, saying that:

Good stuff needs time to mature

This is absolutely true ;-) I would just extend it a bit:

Good stuff needs time AND a lot of energy to mature

Nick, mate, a big thought in your direction, you did such a great job!

Coming challenges are big, again, but first … there are coming! And second, they are super interesting!

A last one now, about “vision” :-)

Despair, Inc)

 

But gosh, now, I just want to sit down with a good grappa, and to appreciate this moment.

LinkedIn vs. Xing

Fast comparison between LinkedIn and Xing.

Xing

  • November 1, 2003 – 5 1/2 years old
  • 7 million members
  • 26’000 groups
  • 16 languages
  • 600’000 paying members
  • 240 employees from 22 nations

LinkedIn

  • May 5, 2003 – 6 years old
  • 40 million members, thereof 10 million in Europe and 800’000 in France
  • 300’000 user groups
  • 4 languages
  • 345 employees

My LinkedIn profile (member since March 2004, i.e. more than 5 years)

My Xing profile (member since November 2005).

The Innoveo LinkedIn profile and the Innoveo Xing profile.

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.

Gosh, 37 years old!

Yes, today is my birthday. 37 years old.

Thanks to Laurent and Mathieu for their wishes via Twitter.

And thanks to Stephen, Thomas, Patrick, Robert, Géraldine for their nice words via Facebook.

And thanks to all my friends and colleagues who have sent me a mail, as Martine, Doris, Bruno, Manu, Olivier, Andreas, Salah.

And thanks to all, my friends and family, who has contacted me per telephone today.

And thanks to my wife and son, Laurence and Julien, for their surprise this morning :-)

Special thanks to Martinique for her Frangipani (picture taken in Senegal).

birthday

And to the Xing team for their virtual birthday cake ;-)

birthday

From an Innoveo CI/CD point of view, Andreas (our designer) won the price ;-)

birthday

A year more, but thanks to everybody, a nice and brilliant day!

PS: yesterday evening, we had a cool dinner at “La Table de Louise”. Very nice local, very friendly and professional service, great food, and … 3 birthdays to celebrate the same evening at 3 different tables :-)

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