Need advice about which tool to choose?Ask the StackShare community!
Heroku Postgres vs Oracle: What are the differences?
What is Heroku Postgres? Heroku's Database-as-a-Service. Based on the most powerful open-source database, PostgreSQL. Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management.
What is Oracle? An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism. Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
Heroku Postgres belongs to "PostgreSQL as a Service" category of the tech stack, while Oracle can be primarily classified under "Databases".
"Easy to setup" is the top reason why over 27 developers like Heroku Postgres, while over 36 developers mention "Reliable" as the leading cause for choosing Oracle.
MIT, Bodybuilding.com, and Seat Pagine Gialle are some of the popular companies that use Oracle, whereas Heroku Postgres is used by Open Humans, PullReview, and Churn Buster. Oracle has a broader approval, being mentioned in 106 company stacks & 87 developers stacks; compared to Heroku Postgres, which is listed in 74 company stacks and 38 developer stacks.
Considering moving part of our PostgreSQL database infrastructure to the cloud, however, not quite sure between AWS, Heroku, Azure and Google cloud. Things to consider: The main reason is for backing up and centralize all our data in the cloud. With that in mind the main elements are: -Pricing for storage. -Small team. -No need for high throughput. -Support for docker swarm and Kubernetes.
Good balance between easy to manage, pricing, docs and features.
DigitalOcean's offering is pretty solid. Easy to scale, great UI, automatic daily backups, decent pricing.
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 Heroku Postgres
- Easy to setup29
- Follower databases3
- Dataclips for sharing queries3
- Extremely reliable3
Pros of Oracle
- Reliable44
- Enterprise33
- High Availability15
- Expensive5
- Hard to maintain5
- Maintainable4
- Hard to use4
- High complexity3
Sign up to add or upvote prosMake informed product decisions
Cons of Heroku Postgres
- Super expensive2
Cons of Oracle
- Expensive14
Sign up to add or upvote consMake informed product decisions
What is Heroku Postgres?
What is Oracle?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Heroku Postgres?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Heroku Postgres?
What tools integrate with Oracle?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+25
+24
+20