Exchange vs. Domino

  • Hallo,


    wir haben seit geraumer Zeit einen Domino-Server im Einsatz (momentan 6.5) mit ca. 180 Usern und 3 Anwendungen.


    Es kommt immer wieder das Thema auf, warum wir nicht auf 'nen Exchange Server wechseln, etc.


    Könnt ihr mir vielleicht die die Vor- und Nachteile nennen, die euch so durch den Kopf gehen, warum man zu Exchange wechseln sollte bzw. was dafür spricht bei Domino zu bleiben?


    Ich hör stellenweise nur, dass es bei Exchange nicht so viele "Macken" gibt, dass das Webmail schneller ist, Mail over Wap, etc pp. Nun such ich etwas, das Domino kann, Exchange aber nicht...


    Danke, Timo

    2 x Domino Server (Clustered) 6.5.3 @win2003 bzw. @win2000
    1 x Domino Server 6.5.3 Suse 9.2 (Webserver)

  • Hi,


    wenn Du nur Mail und Kalender machst und auf geil auf virenanfällige Clients bist, dann kannst Du Exchange nehmen.


    Wenn Du richtig Grupware mit Workflow, Replikation, verteilte Anwendungen und Ähnliches machen willst, dann bist Du bei Domino genau richtig.


    ansonsten Suche einfach mal im Internet nach detaillierten Vergleichen, wie z.B. diesen hier.

  • Hier ein Artikel.


    ---------------------------
    Customers often ask me about the pros and cons of Domino versus Microsoft Exchange. After evaluating each customer’s requirements I am often compelled by the data to recommend Domino. There are several factors that differentiate companies with respect to the appropriateness of messaging and groupware technologies. There is no single, somehow correct solution. Factors such as company size, in-house application development, network infrastructure, staffing and facilities, and budget are all examples of key considerations.


    As a consultant working with both Domino and Exchange I see four principle advantages to Domino: (1) integrated infrastructure; (2) groupware development; (3) knowledge management; and (4) return on investment.


    Mature Integrated Infrastructure Solution


    Compared with Exchange Domino provides a more tightly integrated infrastructure, a and a more coherent user experience and a consistent administrative framework. Through a single set of servers Domino delivers an intelligent combination of messaging and online discussions; calendaring and scheduling; directory services; security administration and access control; intranet and groupware applications; database and database integration facilities; Internet standards-based technologies; forms and workflow; and application development capabilities. Domino delivers all of these services through a single, tightly integrated server infrastructure and a single client application.


    The breadth of capabilities and the depth of integration offered by Exchange is markedly less comprehensive. This is understandable given that Exchange is a less mature product. The concept of integrated infrastructure solutions is relatively new to Microsoft. Microsoft’s Back Office suite of servers is, in marketing terms, a duct tape bundle. The only thing the servers have in common, outside of a few APIs, is that they all run on Windows NT. Also, NT itself does deliver the performance or the scalability needed for large messaging systems.


    Other examples include is public key infrastructure technology and database connectivity. Microsoft has almost no plan for the integration of PKI technology with Exchange while Domino already supports X.509 certificates in the NAB. Domino has the ability to integrate with a variety of back end-database systems using enterprise technologies such as DECS as compared with a non-scalable workstation-side API such as ODBC.


    Robust Groupware Development Platform


    From the development perspective Microsoft offers industrial-strength general purpose development tools and attempts to link these with Exchange to create a groupware application development environment. With Domino, specialized development tools, a rich and powerful set of built-in functions, and native APIs expose the workflow and database capabilities of the Domino engine directly to developers. Despite their myriad development tools, Microsoft remains far behind Lotus in this area. Developing on Domino


    Superior Knowledge Management by Design


    Lotus has been and remains the established leader in the areas of groupware, business process reengineering through technology, and knowledge management. While many software companies have jumped on the KM bandwagon Lotus has been at the genesis of this discipline. Though much underrated by the press, products like Sametime which will be tightly integrated with Domino demonstrate Lotus' sophisticated and expanding vision for knowledge management. Microsoft on the other hand has flooded the marketplace with client-side communication and collaboration tools without a coherent plan for the back office other than NT, SQL Server, IIS, and Exchange; but even these products lack integration when compared with the sophisticated simplicity of Domino.


    Microsoft's version of KM is frankly simplistic. Microsoft would have customers believe that e-mail, calendars, shared folders, bolt-on workflow engines, general purpose development tools, and a lot of marketing add up to 'knowledge management' but it seems apparent from this approach that they are still learning in this area.


    Return on Investment


    CIOs hoping to achieve a return on investment through integrated infrastructure solutions should look to Domino, particularly if they are developing or planning to develop in-house applications. If, on the other hand, the organization foresees several years to come in which only basic e-mail and groupware capabilities are needed then there could be an argument for Exchange, although the differences in total cost of ownership between Domino and Exchange are not typically decisive factors in themselves.


    If a company invests in Domino they are spending perhaps more than they would for Exchange but the potential benefits are much greater. A number of readily available studies show impressive ROI for companies willing to go all the way with Lotus Notes and Domino. It is important to note that for a business to be successful with Domino there must be a high-level commitment to the integration of this technology with fundamental business processes.


    Conclusion


    The development tools and capabilities of Domino for groupware and intranet applications are superior to those of Exchange. Domino represents a much more complete knowledge management framework benefiting directly from Lotus' years of experience in this area. The real power of Domino derives from delivering applications and data through a single integrated infrastructure. Total cost of ownership is not sufficiently different between Domino and Exchange to be a decisive factor. Companies willing to act decisively and to persist in achieving an enterprise wide implementation of Lotus Notes and Domino are likely to realize a substantial return on their investment.


    -------------------------------------
    Hier ist noch ein Redbook mit Infos.


    http://www.redbooks.ibm.com/redpapers/pdfs/redp3694.pdf


    Marcel

  • Ich kann nur aus meiner persönlichen Erfahrung sprechen, aber aus meiner Sicht ist Notes stabiler, mächtiger (besonders was Anwendung-Programmierung angeht) und sicherer.


    Ich muss aber auch sagen, daß mir damals als frischgebackener NT-Administrator Exchange leichter zu admnistrieren fiel, es ging schneller und unkomplizierter User und Gruppen anzulegen - was sicherlich an meiner MS-Erfahrung und den dünneren Möglichkeiten lag.


    Notes habe ich unter Sun Solaris kennengelernt und wegen meiner sehr geringen Unix Kenntnisse ist mir der Einstieg recht schwer gefallen, auch das Anlegen neuer User ist mir anfangs schwer von der Hand gegangen und kam mir umständlicher vor als bei Exchange. Letztlich ist es aber sicherlich eine Gewöhnungssache, wer mit Notes großgeworden ist und dann Exchange administrieren muß, der wird sicherlich das genaue Gegenteil behaupten.


    Schon allein mit Hinblick auf die häufig aufgedeckten Sicherheitslücken im Outlook Client würde ich Exchange ungern empfehlen wollen. OWA funktioniert zwar grundsätzlich, Inotes kommt mir aber "stabiler" vor, hat in meiner Konstellation weniger Ärger gemacht.




    Letztlich hatte ich bei beiden Systemen auch Problemfälle gehabt welche sich aber unter Notes meistens mit etwas Erfahrung wesentlich schneller und besser lösen ließen. Meine Empfehlung würde bei Notes liegen.