Need advice about which tool to choose?Ask the StackShare community!
Oracle vs Vitess: What are the differences?
- Storage: Oracle is a traditional RDBMS which stores data in a single centralized database, while Vitess is a database clustering system for horizontal scaling that partitions data across multiple instances.
- Sharding: Oracle does not natively support sharding, whereas Vitess has built-in support for sharding, enabling automatic horizontal scaling of data storage.
- Cloud-Native Approach: With Oracle, managing databases in a cloud-native environment can be challenging due to its monolithic architecture, whereas Vitess is designed with a cloud-native approach, making it easier to deploy and manage in cloud environments.
- Open Source vs. Proprietary: Oracle is a proprietary database system with licensing fees, while Vitess is an open-source project maintained by the CNCF, allowing users to utilize it without any licensing costs.
- Dynamic Schema Changes: Vitess supports seamless online schema changes without downtime, a feature that Oracle may find challenging to implement efficiently, especially in large-scale environments.
- Compatibility with MySQL: Vitess acts as a middleware between applications and MySQL databases, providing features like connection pooling, load balancing, and query rewriting, enhancing scalability and performance which Oracle might not offer in a similar fashion.
In Summary, Vitess offers a cloud-native, horizontally scalable, open-source alternative to traditional RDBMS like Oracle, with built-in sharding, dynamic schema changes, and compatibility with MySQL.
We have chosen Tibero over Oracle because we want to offer a PL/SQL-as-a-Service that the users can deploy in any Cloud without concerns from our website at some standard cost. With Oracle Database, developers would have to worry about what they implement and the related costs of each feature but the licensing model from Tibero is just 1 price and we have all features included, so we don't have to worry and developers using our SQLaaS neither. PostgreSQL would be open source. We have chosen Tibero over Oracle because we want to offer a PL/SQL that you can deploy in any Cloud without concerns. PostgreSQL would be the open source option but we need to offer an SQLaaS with encryption and more enterprise features in the background and best value option we have found, it was Tibero Database for PL/SQL-based applications.
We wanted a JSON datastore that could save the state of our bioinformatics visualizations without destructive normalization. As a leading NoSQL data storage technology, MongoDB has been a perfect fit for our needs. Plus it's open source, and has an enterprise SLA scale-out path, with support of hosted solutions like Atlas. Mongo has been an absolute champ. So much so that SQL and Oracle have begun shipping JSON column types as a new feature for their databases. And when Fast Healthcare Interoperability Resources (FHIR) announced support for JSON, we basically had our FHIR datalake technology.
In the field of bioinformatics, we regularly work with hierarchical and unstructured document data. Unstructured text data from PDFs, image data from radiographs, phylogenetic trees and cladograms, network graphs, streaming ECG data... none of it fits into a traditional SQL database particularly well. As such, we prefer to use document oriented databases.
MongoDB is probably the oldest component in our stack besides Javascript, having been in it for over 5 years. At the time, we were looking for a technology that could simply cache our data visualization state (stored in JSON) in a database as-is without any destructive normalization. MongoDB was the perfect tool; and has been exceeding expectations ever since.
Trivia fact: some of the earliest electronic medical records (EMRs) used a document oriented database called MUMPS as early as the 1960s, prior to the invention of SQL. MUMPS is still in use today in systems like Epic and VistA, and stores upwards of 40% of all medical records at hospitals. So, we saw MongoDB as something as a 21st century version of the MUMPS database.
Pros of Oracle
- Reliable44
- Enterprise33
- High Availability15
- Hard to maintain5
- Expensive5
- Maintainable4
- Hard to use4
- High complexity3
Pros of Vitess
Sign up to add or upvote prosMake informed product decisions
Cons of Oracle
- Expensive14
