Likelihood to Recommend Our organization found Cloudant most suitable if One, a fixed pricing structure would make the most sense, for example in a situation where the project Cloudant is being used in makes its revenue in procurement or fixed retainer — thus the predictability of costs is paramount; Two, where you need to frequently edit the data and/or share access to the query engine to non-engineers — this is where the GUI shines.
Read full review I could think of a couple but the obvious is in Fintech and Retail, because of the amount of transactional and event level data for global operations. It is imperative to have a solution that can handle such large scale date, in real-time and batch delivery for inbound and outbound delivery, and ultimately ensuring that workload management is supported in some cases for around the clock SLAs.
Read full review Pros For us, performance and scalability is the key, and Cloudant DB backed by CouchDB is scalable and performant. IBM Cloudant dB is very easy to provision for sandbox, development, QA as well as production. Support for Java for CouchDB app server analytics enables a greater control for over developers. Schema free oriented very easy to program and build applications on it. We love it!! Read full review DB2 maintains itself very well. The Task Scheduler component of DB2 allows for statistics gathering and reorganization of indexes and tables without user interaction or without specific knowledge of cron or Windows Task Scheduler / Scheduled jobs. Its use of ASYNC, NEARSYNC, and SYNC HADR (High Availability Disaster Recovery ) models gives you a range of options for maintaining a very high uptime ratio. Failover from PRIMARY to SECONDARY becomes very easy with just a single command or windowed mouse click. Task Scheduler ( DB2 9.7 and earlier ) allows for jobs to be run within other jobs, and exit and error codes can define what other jobs are run. This allows for ease of maintenance without third party softwares. Tablespace usage and automatic storage help keep your data segmented while at rest, making partitioning easier. Ability to run commands via CLI (Command Line Interface) or via Control Center / Data Studio ( DB2 10.x+) makes administration a breeze. Read full review Cons It was only after we went with the cloud-based solution that IBM rolled out an on-premise version. We found that a 3rd-party ODBC driver was required for a few applications that needed to pull data out of Cloudant. The sales process was difficult because the salesperson we used was not as versed on Cloudant as I had hoped. Read full review The relational model requires a rigid schema that does not necessarily fit with some types of modern development. Proprietary database, requires a lot of Hardware for its good performance and its costs are high. As data grows in production environment, it becomes slow. Read full review Likelihood to Renew the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about
Read full review The DB2 database is a solid option for our school. We have been on this journey now for 3-4 years so we are still adapting to what it can do. We will renew our use of DB2 because we don’t see. Major need to change. Also, changing a main database in a school environment is a major project, so we’ll avoid that if possible.
Read full review Usability It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.
Read full review You have to be well versed in using the technology, not only from a GUI interface but from a command line interface to successfully use this software to its fullest.
Read full review Reliability and Availability it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.
Read full review I have never had DB2 go down unexpectedly. It just works solidly every day. When I look at the logs, sometimes DB2 has figured out there was a need to build an index. Instead of waiting for me to do it, the database automatically created the index for me. At my current company, we have had zero issues for the past 8 years. We have upgrade the server 3 times and upgraded the OS each time and the only thing we saw was that DB2 got better and faster. It is simply amazing.
Read full review Performance very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.
Read full review The performances are exceptional if you take care to maintain the database. It is a very powerful tool and at the same time very easy to use. In our installation, we expect a DB machine on the mainframe with access to the database through ODBC connectors directly from branch servers, with fabulous end users experience.
Read full review Support Rating Very happy by the commitment given by the team which has been really good over the last 7 years of usage.
Read full review Easily the best product support team. :) Whenever we have questions, they have answered those in a timely manner and we like how they go above and beyond to help.
Read full review In-Person Training the material was very clear and all subjects have been handled
Read full review Online Training online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers
Read full review Implementation Rating Test the architecture on CouchDB helped us to address initial design flaws. The migration to Cloudant as such was very painless. We have migrate our replication system to Cloudant Android Sync for mobile devices. We have regular informal contact with the Cloudant leadership to discuss our use cases and implementation strategies. Read full review db2 work well with the application, also the replication tool can keep it up
Read full review Alternatives Considered The feature-set, including security, is very comparable. Overall, IBM's services added to the product are mature and stable, although product support and engineers could be a little better. Global availability is improving, and Disaster Recover Capabilities are great. Overall, it's very comparable to
MongoDB as a DBaaS offer, available globally and with great documentation.
Read full review DB2 was more scalable and easily configurable than other products we evaluated and short listed in terms of functionality and pricing. IBM also had a good demo on premise and provided us a sandbox experience to test out and play with the product and DB2 at that time came out better than other similar products.
Read full review Scalability The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.
Read full review By using DB2 only to support my IzPCA activities, my knowledge here is somewhat limited.
Anyway, from what I was able to understand, DB2 is extremely scallable.
Maybe the information below could serve as an example of scalability.
Customer have an huge mainframe environment, 13x z15 CECs, around 80 LPARs, and maybe more than 50 Sysplexes (I am not totally sure about this last figure...)
Today we have 7 IzPCA databases, each one in a distinct Syplex.
Plans are underway to have, at the end, an small LPAR, with only one DB2 sub-system, and with only one database, then transmit the data from a lot of other LPARs, and then process all the data in this only one database.
The IzPCA collect process (read the data received, manipulate it, and insert rows in the tables) today is a huge process, demanding many elapsed hours, and lots of CPU.
Almost 100% of the tables are PBR type, insert jobs run in parallel, but in 4 of the 7 database, it is a really a huge and long process.
Combining the INSERTs loads from the 7 databases in only one will be impossible .......,,,,
But, IzPCA recently introduced a new feature, called "Continuous Collector" .
By using that feature, small amounts of data will be transmited to the central LPAR at every 5 minutes (or even less), processed immediately ,in a short period of time, and with small use of CPU , instead of one or two transmissions by day, of very large amounts of data and the corresponding collect jobs occurring only once or twice a day, with long elapsed times, and huge comsumption of CPU
I suspect the total CPU seconds consumed will be more or less the same in both cases, but in the new method it will occur in small bursts many times a day!!
Read full review Return on Investment IBM Cloudant is very secure and we never have to worry about losing data/unauthorized access It is one of the best data backup system and works well Global availability means it is easy to connect to the nearest data center and this reduces load time which is great. Read full review Fast response time by processing optimization and cost reduction by reduced CPU utilization. Nowadays, good performance is a necessary condition for the survival of a company and its sustained growth SQL enhancements are targeted to improve performance, simplify current and new applications, and reduce the development cycle time to market. A CPU reduction at peak times can immediately reduce our TCO by reducing software costs related to CPU utilization. Impressive reductions in memory requirements, which used to limit the concurrent database activity Out-of-the-box savings without changing the database or application Read full review ScreenShots