IBM FileNet Content Manager is a cloud-native content services solution to manage, share and collaborate on content to save employees’ time and improve customer experiences. This ECM solution includes functionality for document management, business process management, case management, content analytics, imaging, records management, and information governance. The IBM FileNet Content Manager content management solution provides the foundation for IBM Cloud Pak® for Business Automation. It uses AI…
N/A
Pricing
Apache Cassandra
IBM FileNet Content Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cassandra
IBM FileNet Content Manager
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Cassandra
IBM FileNet Content Manager
Features
Apache Cassandra
IBM FileNet Content Manager
Enterprise Content Management
Comparison of Enterprise Content Management features of Product A and Product B
Apache Cassandra
-
Ratings
IBM FileNet Content Manager
7.9
22 Ratings
2% below category average
Content capture & imaging
00 Ratings
8.418 Ratings
File sync, storage & archiving
00 Ratings
8.620 Ratings
Document management
00 Ratings
8.422 Ratings
Records management
00 Ratings
7.320 Ratings
Content search & retrieval
00 Ratings
8.220 Ratings
Enterprise content collaboration
00 Ratings
8.022 Ratings
Content publishing & creation
00 Ratings
8.719 Ratings
Security, risk management & information governance
Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.
Well Suited Scenarios: Regulatory Compliance: IBM FileNet Content Manager is ideal for industries with strict regulatory requirements, such as healthcare and finance. It helps organizations securely manage and retain documents, ensuring compliance with data retention policies. Enterprise Document Management: Large organizations that deal with extensive document volumes benefit from FileNet's document capture, indexing, and search capabilities. It simplifies document management across departments. Less Appropriate Scenarios: Small Businesses: For small businesses with limited document management needs, FileNet may be overly complex and expensive. Simpler, more cost-effective solutions may be a better fit.Simple Document Storage: Organizations primarily seeking basic cloud-based document storage without extensive workflow automation or compliance requirements might find FileNet's capabilities excessive for their needs.
Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
IBM FileNet Content Manager's interface is complex and difficult to navigate for some users. IBM should consider improving the user interface to make it more easier and intuitive.
IBM FileNet Content Manager may be difficult to integrate with other applications and systems. IBM should consider improving its integration capabilities to ease connectivity with other systems.
The wide range of customization make it challenging for users to configure the software to find find their specific needs. IBM should simplify the customization process to make it easier for users.
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
It's a great tool for our legacy system however the implementation, management time and lack of a niche provided by IBM makes it a difficult tool to recommend in a fast-paced market.
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra
IBM FileNet Content Manager is a much superior product compared to anything in the market, IBM AI is really great and the ability to automate is really awesome. We also use other IBM products such as RPA and it integrates seamlessly. Compliance is really the USP of IBM FileNet Content Manager
I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.