Yes, it’s incredible , but true. Red Piranha is everything (well , not exactly everything) that I’ve learnt in 7 years of Java consulting, all wrapped up in a nice easy to go bundle. It’s Enterprise software that gets knowledge out of people’s heads and into a PC (no , it’s not as painful as it sounds!).
I hadn’t checked the stats for a while , so I’m astonished to learn that 25,000 people have downloaded a copy from sourceforge. What’s more amazing is that these downloads are for version 1 – a sort of ‘mini Google’. As I write this post the latest (beta) version is being made available to developers. This moves it firmly into the Enterprise Web 2.0 space, adding workflow, rules and rich internet application capabilities (including Ajax and mashups) – more on this blogpost.
By the way , if you’re looking for more information on Enterprise Web 2.0 , you can check out Jerry Bowles blog on this area.
The Irish Computer Society (ICS) has a useful checklist for Irish companies of things to watch out for when setting up an IT contracts.
These items include:
- Take a look at your ‘standard’ contract in the light of recent developments in IT
- Review how you can make your supplier selection process even better.
- Use competitive procurement if possible
- Keep electronic copies of contracts
- Have formal contracts in place
- Watch out for IPR and use source code escrow if necessary
When SAP announced that they were migrating their solution to a full J2EE server stack, I was initially sceptical. While it makes good business sense (after all Enterprise Java server’s are now effectively free), and complemented their decision to open source the SAP DB (now known as Max DB), there was still a niggling feeling at the back of my mind.
Why? Well over the years we’ve learnt a lot of lessons of how to build Scalable Java applications. Even then, some people can’t seem to get it right (No names , but you know who you are). How would SAP people (who I have a lot of respect for as you don’t get to the position SAP is within the industry without getting at least something right) react to this strange new Java world. Would they shed all past baggage and dive in with the enthusiasm of College Graduates? Or would they take a ‘not invented here’ attitude and hack together something in Java along the lines of what they were used to.
I suspected the latter , and fully expected to end up cleaning up some mess of a CRM or ERM system. However, I am pleasently surprised with SAP’s Java Website. On a pure Java level, it approaches the efforts from Oracle , IBM and BEA. If SAP are making this amount of effort to promote Java best practice, then there may be hope after all.
Final question: If this goes the way SAP is planning, at what point does it’s installed base get counted as part of the Market share of J2EE servers. What percentage of the market would it have? A healthy and very profitable 10%? Certainly the strategy (and the Market share) is very close to Oracle , which also bundles it’s (10g) App server with it’s main product (a Database rather than a CRM or ERP Solution).