It’s been a while after VMware acquired Zimbra. In a VMware Console blog, VMware CTO Steve Herrod explained how Zimbra fits in VMware’s mission to simplify IT.
Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.
Today I attended a seminar on Zimbra at VMware engineering weekly tech talk. Kevin and Maria from Zimbra team explained both client side (browser based and desktop) and server side architectures. They also introduced one of the biggest implementations with a service provider, from number of subscribers to the hardware configurations. I am very impressed by the scalability Zimbra offers. This answers partially my question, “Why did they want to create a new mail/collaboration product?”
At the end of the seminar, we got a link to an architecture document. This is a public resource. Although written in 2005, this 33 page document gives a great in-depth introduction on the architecture. Better than describing what it is, the document also explains why and how they made key architectural choices. Highly recommended for anyone, even though you are not really interested in collaboration software. It’s a great case study for software and system architecture design.
BTW, the Zimbra team is hiring. Check it out here.