Likelihood to Recommend You should go for using it in particular if you are going to be build code once run everywhere kind of things and you want to not write most of the backend on your own. As AWS Amplify can take care of a lot of backend things for you and you can manage most of the stuff from front end coding. perfect for using in react/ flutter apps. Additionally better to use when you are going to use other AWS service and don't want to scatter things around
Read full review 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.
Read full review Pros UI and design of the AWS Amplify for easier setup painless user flow for react, angular etc easier setup using CLI with effective questions. Read full review 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. Read full review Cons AWS Amplify init ends up changing the cloud. there should be deploy kind of thing confusions between Front end backend as both codes get mixed. this should be kept separate better documentation with use cases Read full review User interface needs to be modernised. Read full review Alternatives Considered Its AWS take on the
Firebase kind of system for providing backend as a service. Although
Firebase has advantage of bigger community, better documentation and code examples; AWS Amplify is creating its own space where you will be going to use AWS products and Infrastructure in your project. Amplify Dynamo DB and GraphQL have clear cut advantages that have no direct alternative in
Firebase as real time db and firestore documents both lack versioning.
Read full review 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.
Read full review Return on Investment saves time on righting backend interfaces easier to setup with react/ react native lambda functions can be used to extend functionality Read full review 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. Read full review ScreenShots