James Governor's Monkchips

VMware Zimbra: Integration without Context Shift

Share via Twitter Share via Facebook Share via Linkedin Share via Reddit

Stephen did his usual excellent job of explaining the the VMware Zimbra acquisition with a Q&A. Seriously – read the analysis. I already fed some of my thoughts into his post, but there are a couple of other things I wanted to mention.

Zimbra’s awesomesauce

Zimbra remains probably the single best implementation I have seen of real plasticity in a GUI, where information pops in context, without needing to move to a new screen or click through. Addresses turn into Google Maps, or sit up and beg to become Contacts. Zimbra was designed to be a plastic front end – not just for email, but any kind of back end web service.

RedMonk actually ran on Zimbra for collaboration for a while but the performance of the system was disappointing. This was because of the third party host we were using, rather than the Zimbra architecture itself. I know for example that Headshift ran its own server, and it was blazing fast. Another reason performance may have disappointed was that this was before the browser performance war really started heating up, driven by competition from the awesomely speedy Chrome browser.

On Premise Good?

As I just mentioned, Zimbra was never designed for cloud only deployment- on the contrary it can work just fine as an on premise open source email, messaging and collaboration server. Oh yeah- works well with Outlook too! Yahoo never seems to have decided one way or another what to do with its acquisition. VMWare has a much clearer view: Zimbra will fit neatly into a hybrid cloud play, potentially with an associated storage play for parent company of the parent company EMC.

Channels

Just before the VMware deal was announced I met a UK Zimbra reseller called In-Tuition. I was pretty skeptical about making a play to compete with Microsoft Exchange with a piece of software owned by Yahoo, which is not exactly renowned for its enterprise chops.  But they must have known something we all didn’t… 😉

Suffice to say Zimbra is and always was designed for enterprise class deployments. Its very much a business tool.

Summing Up

The collaboration market is in play again – customers are fundamentally reassessing strategies defined in the 1990s. Lotus is back. Google is making headway. Microsoft is not going to give up without a fight. And now VMware has a play. Different buyers? Perhaps. But the same people that make virtualisation decisions also make Microsoft infrastructure decisions. VMware CEO Paul Maritz wanted a pushback if customers decided to can VMware in favour of Windows Virtual Services. Now it seems he has one.

I am looking forward to seeing what happens when Zimbra meets SpringSource (another recent VMware acquisition): That could be back end to front end goodness, and a growing set of Java APIs for VMware to steward and grow a community around.

For an enterprise looking for a mail server – Zimbra can definitely do a solid job. But its where it goes from there that’s more interesting. Java and Javascript is increasingly common as a skillset and programming approach. Zimbra was architected to the pattern.

As I said in a recent post

Products like IBM WebSphere Portal and SAP Netweaver Portal were supposed to bring much improved user interaction models to enterprise IT, but unfortunately traditional systems-focused IT departments, rather than user interaction specialists and their web brethren, did the work. People like Josh Porter generally weren’t invited to the party. Portals were built to support IT systems and data, rather than users

Its not just email that’s up for grabs. The 1990s portal is also looking tired. I wouldn’t be surprised to see VMware make a plasticity play.

10 comments

  1. VMware Zimbra: Integration without Context Shift http://bit.ly/bw37Fe some thoughts on why i think the deal could make a lot of sense
    This comment was originally posted on Twitter

  2. Analysis from @monkchips on why Zimbra is more than just a mail server for VMW http://bit.ly/bw37Fe (See where we’re heading?)
    This comment was originally posted on Twitter

  3. James Governor’s Monkchips » VMware Zimbra: Integration without … http://bit.ly/bxaIFA
    This comment was originally posted on Twitter

  4. James Governor’s Monkchips » VMware Zimbra: Integration without …: Stephen did his usual excellent job of explai… http://bit.ly/d6JZJf
    This comment was originally posted on Twitter

  5. Interesting points James – we’re very excited about the VMWare deal and what it will mean for us and the channel.

    We need an extremely strong stack… Does VMWare + Spring + Zimbra do it, no I don’t think so as I believe there are more pieces of the puzzle which need to be added, but it’s a dam good starting point and a much stronger position than where we were last year…

  6. Zimbra’s ability to integrate without context shift: http://bit.ly/amVkjq – my thoughts here: http://bit.ly/a1yJaA
    This comment was originally posted on Twitter

  7. Analyst commentary on #Zimbra acquistion http://bit.ly/bf3OBr
    This comment was originally posted on Twitter

  8. Zimbra needs major work to scale beyond the “user lives on a single mail server” model. I think VMware could provide the resources to do that.

    If mail accounts are held in a pool that any ZCS mailbox server can access, then “all” (ha!) you need to do would be to add more Zimbra mailbox vApps to your cluster (assuming hardware resources available)

  9. I’ve done some playing with Zimbra, and while a bit of extra development could, I’m sure, make it a more efficient piece of software, I wouldn’t be so quick to pass off it’s performance faults as being a deployment specific problem. It’s sort of a “throw RAM at it and pray,” problem, and thankfully that works.

    One of the reasons Zimbra gets a bad rap, at least in the circles I travel in, is that the competing UNIX stack (postfix/dovecot/etc.) is a magnitude more efficient on system resources. So it’s the kind of thing that if you need it, you have to be willing to pay for (in some way) and that you probably want to try and avoid unless you really need it.

  10. […] Governor recently posted an interesting piece on how Zimbra can be leveraged to integrate other applications without context shift – i.e. […]

Leave a Reply

Your email address will not be published. Required fields are marked *