Quote:
Originally Posted by jholder Welcome to the Forums!!
1) Can you come up with a migration script
2) How Labor intensive will migration be |
Hello,
Ok, after posting a question a week or so ago about this in this forum, and searching, I found a thread on why you shouldn't "pull apart the pieces" so to speak. I think it's funny but sad that a Zimbra employe said, "Well, we sell Zimbra and so we know what people want, and this is it!" Clearly, there are many people who
don't want that, as can be seen in these forums.
Is anybody interested in investigating the creation of a "Zimbra Light"??
There are two huge problems with this theory; namely, the fact that Zimbra now has to support everything, and the fact that it's hard to integrate Zimbra into solutions that don't use the bundled packages.
The "easy install" and "guaranteed known versions of sw" reasons for bundling the whole kit-n-kaboodle together I can see from a Zimbra corporate standpoint. They need to support this stuff. But, given my Linux experience, frankly I don't care; I just want an interface I can drop into place over existing services because
I have already tuned those services for performance on my hardware. Plus, how do we know that a) The servers included with Zimbra are configured properly, and b) if we want to re-configure them it won't break things?
For example: does the MySQL engine use MYISAM tables, or something that is robust and transaction-safe? Can I make it transaction-safe if it isn't? How do I fix the tables when they inevitably trash themselves? (Anyone using MySQL in a mission-critical situation, without having a cluster of DB machines, is asking for trouble - and from what I've seen it's not trivial to install Zimbra on a cluster of machines, nor is it cost-effective. Postgres would have been a much better choice here.)
Next comes the integration problem. I'm working on a major open source stack for a vertical market. I'd love to use Zimbra's functionality, but a) my use is too data-critical to use MySQL, and b) I find the extent to which Zimbra seems to modify the system unacceptable. Yeah, I could use a virtual server, but running two copies of an OS and of a DB and of an EMail server and of Tomcat or JBoss is inefficient (in terms of resource and therefore electricity usage, and in terms of having to maintain two stacks).
Store appointments in SQL database, and mail as files on disk via Cyrus IMAP. Build services using Tomcat that access those data stores. Why do things need to be more complex than that?
Don't get me wrong, the folks at Zimbra have gone very far in giving us a valuable replacement for exchange - but in their push for enterpriseyness, they make things hard on some of us who really know how to make things run and run reliably.
Cheers,
-JC