Slashdot Mirror
IBM's Inexpensive Notes/Domino Push Against MS
Deviant writes "Speaking as an IT consultant, the one big gap in the Linux stack is in messaging / collaboration. MS Outlook with Exchange is a fine product on which many businesses truly rely, and it is almost impossible to match on Linux — server or desktop. The one competitor to MS in this space has been IBM's Lotus Notes / Domino, which has always had the general reputation of being expensive, bloated, and unfriendly. I certainly wouldn't have considered it for the small businesses that we usually sell on MS's SBS server product. That is why I was truly surprised to hear about the new Domino Express Licensing and Notes 8. This is a product that has native server and client versions for both Mac and Linux. Notes 8, now written in Eclipse, also includes an integrated office suite, Lotus Symphony. This could conceivably let a user do all of their work in one application. And you can now license the server and client components together for as low as $100/user. It's packaged for companies of 1,000 seats or fewer. Is this the silver bullet to take out the entire MS stack — server, client, and Office? Or will IBM drop the ball yet again?"
I don't see that at all, but the problem isn't just the MS 'stack' from client application to server, but the fact that MS is pushing all sorts of integration and features that competitors don't have.
Everyone else (StarOffice, Lotus Notes) is so busy playing catch-up to compete on features, and once Microsoft hooks these businesses on things like SharePoint and what-not, well, suddenly switching to the competition means you lose functionality, and productivity in doing things "the old way" again.
It's a bad deal all around and I really would like to see Microsoft open up things like SharePoint for interoperability, but if you honestly think that'll happen in short order, you're living in Candy Land.
...and now with the lower price it's just bloated and unfriendly ?
Seriously though, I have used Lotus Notes in a global corporation which made extensive use of custom forms, applications, groups and the whole shebang in addition to relying heavily on the calendar for scheduling. It was a terribly counter-intuitive and unresponsive piece of software, and I'd rather pay for Exchange than having a Lotus Notes installation for free, despite being known as the anti-Microsoft advocate in my company.
Oh, I can't help quoting you because everything that you said rings true
Outlook is one of the most user-acceptance tested applications in the world. Really, it is.
Outlook just happens to work really well with Exchange.
Exchange/Outlook just happens to plug really well with SharePoint/MOSS (for document sharing, workspaces, etc).
The both just happen to use SQL Server, and of course the whole security model just happens to be based in AD, which in turn just happens to be a Windows Server only technology.
It's all very integrated, and actually works very well with not too much knowledge. Seriously, I think 99% of the people on this site could setup the system above I just outlined in a day.
Why? Well, you start with Outlook and before you know it, you've got the whole ecosystem. It's designed to plug in as easily as possible to enable you to give cash as easily as possible to Microsoft.
Clever eh?
throw new NoSignatureException();
It's possible, yes. If you limit your service.
As an example, Exchange uses shared mail by default - but only within the storage group for that one mailbox.
Up until very recently, the maximum size per storage group in the Information Store was 16Gb. I believe it's now either 75Gb or 16Tb, depending on the license for the server. 16Tb is fine, but even 75Gb - for a shared store - is a bit constrained. It doesn't need a huge number of large mailboxes to start giving you serious problems, and in a large enterprise that will happen very quickly.
The way you work around that is simple - you either spend a lot of time monitoring your information stores and doing capacity management, or you set hard quotas at low values.
Anecdotally, most of the people I know that have very low quotas on their work mail systems are on Exchange Servers, whereas most of the people I know with gigabytes of mail aren't.
Now contrast this situation with Domino, which has a shared mail system which is switched off by default. Nobody uses it because they know it introduces these kinds of scaling issues. (By the way, even Microsoft recommends that you should ignore shared mail when capacity planning.)
Everyone gets their own database, which means that monitoring, moving, replicating and generally managing users is much easier.
That's just the start of it. Uptime? In my experience, the shared storage system that Microsoft's clustering solution requires reduces uptime, not increases it. Domino servers fail over faster because they have no shared resources.
Exchange's architecture does show strain. If you're a Microosft Gold Partner and can call on them to advise you, then fine - otherwise, good luck to you!
This is exactly right. Everything ties together so tightly that once you get one piece you might as well take the whole. You buy Office, which runs only on Windows and which comes with Outlook. You want to use that for email so that means Exchange. Exchange depends on MS Active Directory so that means storing all your user accounts on the MS server and authenticating against that. As long as you have these MS servers for authentication you might as well do your file/print sharing there. As long as you are doing your file sharing there you might as well use DFS replication and put another server in the branch office. Once you are running Exchange you might as well run Outlook Web Access and that means IIS. Once you are already hosting that on IIS you might as well host your other web pages there. Since you are hosting your web pages there you might as well use MS SQL as the backend as well as Sharepoint for the intranet page - etc etc.
They even are nice enough to bundle all of this into one (relatively by MS standards) inexpensive product called SBS Premium. The big catch is that you have to run all of it on one server. As the buisiness expands, and they have already got you depending on it all, they really sting you with the licensing increases involved in buying the full versions of all the various software and their associated Client Access Licenes (CALs) so that you can seperate into multiple servers. When you get bigger still and need clustering and redundancy you need to throw still more servers and more licensing fees at the problem (usually for "Enterprise" products then as well) and that is when they really get you.
I am an RHCE as well as having the full spread of MS certifications - I love Linux and run that and a Mac on the desktop at home. I rarely get to use my Linux knowledge/certifications these days because of all the MS lockin/ubiquity. There are a few places that I would have liked to use CentOS or RHEL for some things but was forced to use the MS product by their insistance on Exchange - and once you have the infrastructure for that there then is no place/need for Linux any more. That is why I submitted this story and have been looking for this solution - the hope that I might actually have something I could sell a buisiness on that would allow me to actually get some Linux out there!
Trust me though when I say that Office/Outlook/Exchange is the #1 reason for half of MS's dominance in the server space. We need something to counter it. I am just really hoping that IBM, with all of its resources and its relative presence in this space, can give it to me...