Likelihood to Recommend Easy integration with the external APIs Workflows can be invoked via REST call Wonderful swagger documentation for process REST APIs REST, MULE, CAMEL, Google Drive, and Box features are available with Alfresco Process Services The micro-service version deployment should be well documented and needs improvement
Read full review If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read full review Pros Basic workflows are easy enough for casual users to set up and utilize. Cloud sync capability provides a great way to share documents with third parties and to use as a backup system for critical documents. Alfresco mobile app makes it easy for those on the road to access, approve and share documents. Folder rules are easy to set up and make assignment of metadata easier to automate. Read full review Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth. Read full review Cons Alfresco Process Services and Alfresco Application Development Framework integration makes for best functionality/application of ECM. Use case alignment - Marketing content and documentation of specific business requirements and user stories being available as reference material/documentation. Integration with multiple silos for content. Read full review Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough. Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling. Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement. Read full review Likelihood to Renew As per the current market and the line of products that are available for content and document management system, Alfresco is a very good option compared to other systems in terms of features and cost. Plus the community support is great. Also since the product is open source, it can be extended or understood in a better way.
Read full review Usability Alfresco Content Services' UI has never been its strength from the beginning. Therefore, rating it from a usability standpoint, I will not rank it high. However, Alfresco Content Services can easily be integrated with any application and leveraged as a backend CMS or DM system. With the new Angular-based UI approach, it's very much possible to create custom UI on top of it as required.
Read full review Support Rating I am not big fan of Alfresco Content Services' support; it works on its own speed and sometimes it becomes challenging to achieve business needs. However, I appreciate regular delivery of security patches and updates
Read full review Implementation Rating Process was relatively smooth and overall, downtime minimal. MSI was very responsive to our needs and made the transition easier than it otherwise might have been.
Read full review Alternatives Considered All software has some pros and some cons. Alfresco has some good pluses, and suits our environment very well. It fit perfectly in the place that we are working on. That is why we decided to go with this software. Overall, the kind of content management that needs to be done in an organization is what would determine which software to use.
Read full review There are a lot of similarities between
Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Read full review Return on Investment Instant document lookup - No paper files to mail which saves in all areas of postage, truck delivery, physical storage warehouse space, printing, etc No longer losing important documents - Previously with paper files things would go missing and those could be costly reports/assessments. Ability to secure documents and provide access to only those who should be allowed to see that content Read full review Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used. Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients. Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money. Read full review ScreenShots