This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Domino VS. Websphere ~Justin Minluternivu 19.Dec.02 08:12 PM a Web browser Applications Development All ReleasesAll Platforms
I think the best line of demarcation is between "information" and "data". Domino is good at handling "information", while WebSphere (and similar technologies) are best for handling "data". Let's giva a f'rinstance:
A corporation wants to set up a web site to display a large quantity of semi-static content, perhaps multilingual, and incorporating a content-management system and the ability to search that content. They also have a large quantity of highly-structured data to deal with, allowing commercial transactions or an facility to query that data. Should they use Domino? WebSphere? The answer to both questions is "yes".
WebSphere combined with a relational back-end (such as DB2) is absolutely fantastic at dealing with structured data. Developing safe data transactions with controlled commitment that work at breakneck speed is a doddle (relatively) in WebSphere. It isn't so hot for dealing with semi-static content, though, and leaves you with the search engine and content management problems. If you need them, you have to develop your own solutions or develop connectors to off-the-shelf solutions.
Domino, on the other hand, already has the workflow and content in hand -- developing applications to allow content creation, approval and publication is at the very basic level. Navigation is self-updating if views are used, and the multilingual capability is a matter of switching forms to display different fields -- all that's required is a view with a form formula to get the right fields. The document is called for display, and the form comes along for the ride -- the exact opposite of what happens if, say, a JSP is called that needs to look up data for display in the content-management database. Domino does not, however, work with structured data very well at all -- there are advantages to fixed tables that the NSF cannot hope to match, and "relations" in Domino are based on run-time lookups.
In other words, it's horses for courses. Neither solution will do everything, although each can be forced to act something like the other at a considerable cost in development and performance. As often as not, you'll find that both platforms have their part to contribute -- which is what NextGen is all about.
Return to top
. . RE: Domino VS. Websphere (~Justin Minlute... 19.Dec.02) 
Print this page
