HCL Domino vs. Node.js

Domino is best in medium-sized businesses of 20-100 employees. It's too complicated to implement in very small companies unless you have good external resources. It scales up very well for larger companies but the pressures of users wanting particular "brand-name" software can become difficult. If you want a restricted "extranet/portal" system for a limited set of members it's a great system, particularly if you add a Domino CRM on top. Unlike Microsoft, you never have to resort to command-line tools, like PowerShell, in Domino to get things done.

Incentivized

1. Node.js is useful for building one page, fast, light-weight, scalable applications. 2. It is not suitable for building computationally extensive applications, it may lead to bad performance.

Incentivized

• Domino support for policy-based user registration and deployment eases end-user creation.
• User access to databases is simplified via group membership and defined roles.
• Email replication to clustered servers is simplified through connection/replication documents stored centralized address book
• Group calendaring enabled at client level controls.

Incentivized

• Robust
• Fast
• Modern
• Easy to learn
• Allows using JS or TypeScript everywhere
• Supported and maintained actively by the open source community
• Pleasurable to work with
• Reliable
• Simple to learn
• Simple to setup

Incentivized

• User interface needs to be modernised.

Incentivized

• It reduce performance while dealing with heavy computational task.
• Node.js invites a lot of change in code, due to an unstable api.
• Lack of library support.

Incentivized

Node.js is easy and good to use, their support team is also good they always tend to help you, and solve your problem, even we know that Node is free to use and opensource but then also we get support from them but for getting much better results we need to purchase standard or enterprises support provided by them.

Incentivized

We use SharePoint, SQL and Teams but only for the things that they excel in. For example, we use teams for small team interactions (including external participants). We use teams for meetings too. We've discovered that Teams collaboration is not as full-functional as Domino and more importantly, that our members (financial services) do not trust the Open Office365 cloud. SharePoint and Team collaborative features are often blocked in our member organizations. Domino is much easier to identify and unblock at the firewall level. It's much easier to restrict collaboration to approved options in Domino.

Incentivized

There is a smooth and seamless performance for multiple requests as the feedback received from users. and uses one platform to maintain UI and backend.

• The immediate impact on my organization as a non-profit is cost. Enterprise pricing for a Domino solution is exponentially more inexpensive than more popular applications.
• Of the most obvious impacts is user familiarity. Given a vast majority of the employment pool having familiarity with MS products, orienting new employees to Domino\Notes is burdensome. Adoption is slow and resistance is high.
• Hiring Domino administrators and developers is increasingly challenging.
• The recent sale of the Domino platform away from IBM is concerning.

Incentivized

• It helps our business to expand our standard offer with new solutions based on Node.js such as conversation bots.
• It brings avarege 2-3 new clients projects per year, that we couldn't do without it.

Incentivized