Apache Geode is a distributed in-memory database designed to support low latency, high concurrency solutions, available free and open source since 2002. With it, users can build high-speed, data-intensive applications that elastically meet performance requirements. Apache Geode blends techniques for data replication, partitioning and distributed processing.
N/A
IBM Storage Protect
Score 8.5 out of 10
N/A
IBM Storage Protect (formerly IBM Spectrum Protect, or Tivoli Storage Manager) provides data resilience for physical file servers, virtual environments, and applications. Organizations can scale up to manage billions of objects per backup server.
N/A
MongoDB
Score 8.9 out of 10
N/A
MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.
$0.10
million reads
Pricing
Apache Geode
IBM Storage Protect
MongoDB
Editions & Modules
No answers on this topic
No answers on this topic
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
Offerings
Pricing Offerings
Apache Geode
IBM Storage Protect
MongoDB
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Fully managed, global cloud database on AWS, Azure, and GCP
More Pricing Information
Community Pulse
Apache Geode
IBM Storage Protect
MongoDB
Features
Apache Geode
IBM Storage Protect
MongoDB
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Geode
8.7
1 Ratings
2% below category average
IBM Storage Protect
-
Ratings
MongoDB
10.0
39 Ratings
12% above category average
Performance
9.01 Ratings
00 Ratings
10.039 Ratings
Availability
10.01 Ratings
00 Ratings
10.039 Ratings
Concurrency
10.01 Ratings
00 Ratings
10.039 Ratings
Scalability
8.01 Ratings
00 Ratings
10.039 Ratings
Data model flexibility
7.01 Ratings
00 Ratings
10.039 Ratings
Deployment model flexibility
8.01 Ratings
00 Ratings
10.038 Ratings
Security
00 Ratings
00 Ratings
10.039 Ratings
Data Center Backup
Comparison of Data Center Backup features of Product A and Product B
The biggest advantage of using Apache Geode is DB like consistency. So for applications whose data needs to be in-memory, accessible at low latencies and most importantly writes have to be consistent, should use Apache Geode. For our application quite some amount of data is static which we store in MySQL as it can be easily manipulated. But since this data is large R/w from DB becomes expensive. So we started using Redis. Redis does a brilliant job, but with complex data structures and no query like capability, we have to manage it via code. We are experimenting with Apache Geode and it looks promising as now we can query on complex data-structures and get the required data quickly and also updates consistent.
IBM Storage Protect is well-suited for large heterogenous environments, with skilled IT staff on-hand. You need a person (or group of people) to monitor day-to-day operations, tweak schedules where needed and be mindful of things that might go wrong. It is also well-suited if you have other IBM products that integrate well with Storage Protect, like Storage Protect Plus or IBM Defender. It is less suited for small companies, with only one person responsible for IT. Employing Storage Protect would be overkill and use too much time of the administrator.
If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.
Tight integration with Db2. As an IBM product, it works seamlessly with Db2. You can query what is stored in TSM via Db2 itself. You can also use DB scripts to maintain the items being stored there.
Like most of its competitors, Tivoli handles deduplication well.
Provides a GUI for browsing and maintaining items stored there. I rarely use this feature, due to the next item I will post:
Command-line interface directly from my Db2 database servers.
Both client and server-side deduplication, compression and encryption are available.
If the requirements are zLinux and DB2 support then it's the most solid solution.
Can be complex to implement, but once up and running, it is rock-solid and immensely scalable.
Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.
An aggregate pipeline can be a bit overwhelming as a newcomer.
There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.
I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.
Still Experimenting. Initial results are good. we need to figure out if we can completely replace Redis. Cost wise if it makes sense to keep both or replacement is feasible.
In the present, a backup solution is a must-have, but then companies start using a solution for virtual machines, another solution for bare-metal servers, and another solution for their ERP. By using Spectrum Protect you can have all of that in a single pane of glass. This way you can have a simple recovery plan for all your information assets.
NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.
Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.
While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
IBM Spectrum Protect is related to the other IBM Spectrum products listed because it is part of the suite and is also the main backup product for backup and restoration of information. With Veeam it is related as they present competence in different lines of technology, often the integration of both tools can be the best solution for clients looking for a successful backup strategy.
We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.
Tivoli does well running file-level backups, but Exchange is clunky and restores are really hard. With no SharePoint agent, if you use SharePoint you will need another product like AvePoint DocAve. The web-based GUI console is MUCH improved over earlier versions, but you will still need to be a command-line guru to make Tivoli do everything, and local (node) config files still rule. This product was originally ported from Unix and retains may of its 'nix roots.
Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB