Db2 vs. Percona Kubernetes Operators

I have primarily used it as the basis for a SIS - but I have migrated more than a few systems from there database systems to DB2 (Filemaker, MySQL, etc.). DB2 does have a better structural approach, as opposed to Filemaker, which allows for more data consistency, but this can also lead to an inflexibility that can sometimes be counterintuitive when attempting to compensate for the flexibility of the work environment as Schools tend to have an all in one approach.

Incentivized

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

• 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.

Incentivized

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• everything about Db2 is 'heavy', even the Community edition and some of the clients
• difficult to configure for beginners /option overload
• LUW and z platforms have minor inconsistencies that really should be a non-issue
• support seems to be declining in terms of quality/quickness of responses

Incentivized

• Some differences compared to "traditional" MySQL solution.
• Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc.
• The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor.

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.

Incentivized

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.

Incentivized

Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.

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.

Incentivized

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.

Incentivized

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.

Incentivized

Well documented, there was no need to contact support.

the material was very clear and all subjects have been handled

Incentivized

db2 work well with the application, also the replication tool can keep it up

With the other two mentioned above, I needed to have processes and frameworks that executed outside of the environment driving DB management operations. Yes, these are completely different solutions; however, the support you get for framework, library, and language support allows for runtime at a different layer than with other solutions.

Incentivized

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.

DB2 can be configured and can work with a variety of applications as opposed to how it was designed initially to only with with IBM mainframes. It's easy implementation process makes it a good buy for many organizations to scale their applications to be the best in terms of versatility, resilience and application performance

Incentivized

• Time efficiency is the major point to highlight, especially the minimal time this takes while querying a larger set of data.
• Reliability becomes another major factor as the application can be accessed at any point in time.
• Users might initially find it challenging to use the application.

Incentivized

• It allowed us to use k8s on our entire infrastructure.
• Decreased administrative overhead around our db services.
• As it is an open source technology, it cut down our db pricings.