# MySQL vs PostgreSQL -- Choose the Right Database for Your Project

**URL:** <https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097>\
**Category:** Developer Blog Comments\
**Created:** [July 19, 2019, 3:33am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097 "2019-07-19T03:33:20Z")\
**Posts on this page:** 14\
**Page:** 2

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [June 5, 2020, 9:24am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/21 "2020-06-05T09:24:10Z")

</div>

**Vovk**

Your process should accumulate multiple records into a temporary buffer and run a single query with all records at once on regular intervals.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [July 17, 2020, 6:22am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/22 "2020-07-17T06:22:03Z")

</div>

**360digitmg**

I wanted to leave a little comment to support you and wish you a good continuation. Wishing you the best of luck for all your blogging efforts.  
[360digitmg data scientist courses](https://360digitmg.com/india/data-science-using-python-and-r-programming "https://360digitmg.com/india/data-science-using-python-and-r-programming")

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [August 24, 2020, 7:01am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/23 "2020-08-24T07:01:54Z")

</div>

**Raja K Thaw**

Should I prefer PostgreSQL-XL free download as it offers mixed workloads+ COLUMNAR, for MPP proprietary databases ? I am not sure, how hard to convert everything to columnar in PostgreSQL. I think for MySQL we need to resort to MariaDB columnstore. Connect with me on linkedin—\> [https://www.linkedin.com/in…](https://www.linkedin.com/in/raja-k-thaw-9317a615/ "https://www.linkedin.com/in/raja-k-thaw-9317a615/")

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [September 2, 2020, 12:58am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/24 "2020-09-02T00:58:45Z")

</div>

**Thor-x86**

Personally, I use either of those database depend on framework currently in use. As example:  
Laravel (PHP) =\> MySQL  
Django (python) =\> PostgreSQL

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [September 10, 2020, 7:00pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/25 "2020-09-10T19:00:44Z")

</div>

**MindOpener**

1000 record / sec is nothing for both Mysql or Postgres. Latency and response time will start to change depending on the size of the row you’re inserting, how many indexing you have, do you have text, json.   
Mysql (using load data infile) can load 100,000+ rows per second.   
It all depends what your writes need are : (referential integrity, critical transactions). If you need to store data for Audit purpose Mysql and Postgres might not be the best solution. I would look into MemSQL which was built for fast ingestion and analytical queries.

I’m sure Uber did their homework. You don’t switch from one DB to another just because one guy prefers Postgres.   
Research and test (benchmarks) is a must. Lots of biased benchmarks out there that probably don’t match your workload and table structure.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [November 19, 2020, 8:24pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/26 "2020-11-19T20:24:21Z")

</div>

**Matthew Kennedy**

Rails =\> PostgreSQL

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [January 13, 2021, 2:41pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/27 "2021-01-13T14:41:37Z")

</div>

**Peter Labos**

If I understand properly “logging API queries”, this should avoid DB completely. Not really good choice indexing this stuff realtime. Best option is save it to filesystem and then install and use some log processing/searching software or SaaS api. To send files to different company to process it and giving you all the search options even fulltext ones.  
If it is something with more sensitive sata and less volume use some message queue system.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [January 13, 2021, 3:43pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/28 "2021-01-13T15:43:50Z")

</div>

**Peter Labos**

Haven’t check those two services. But I personally would use also some “browser local DB/storage” to move some workload to customers computers, like saving steps (for undo actions). To limit requests you may save their data to server in some time intervals, or only when they switch to different file in project or only on demand (when they hit save button).

And to that “hundreds of thousands of concurrent users”. Start with 100, then 1000 users and only selected registered testers, before you shut down your server with that number of users or before you pay hundreds or thousands of dollars to your server provider for auto scalling servers and not earning a penny on it.

And good luck with a project.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [January 25, 2021, 2:57pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/29 "2021-01-25T14:57:48Z")

</div>

**Saif Ul Islam**

Very interesting article. Me and my friends were just discussing this today, so this article was definitely very helpful. Thank you!

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [January 27, 2021, 9:01am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/30 "2021-01-27T09:01:37Z")

</div>

**Deepak Bharti**

Try to do the batch operations

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [March 10, 2021, 3:13am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/31 "2021-03-10T03:13:45Z")

</div>

**ReverseAds**

Very comprehensive article. I have to admit that many times, I have started a project and then when the project reach its potential, I am starting to thing, why I haven’t selected different database from the begining and speed it up.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 28, 2021, 1:02am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/32 "2021-04-28T01:02:46Z")

</div>

**milan sonkar**

One of the major disadvantages of Postgres apart from what is mentioned here is it does not support Transparent Data Encryption which is a must have feature for storing sensitive information

---

<div class="post-metadata">

**Author:** ![tipseason](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tipseason](https://devforum.okta.com/u/tipseason)\
**Post date:** [July 10, 2022, 9:16pm UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/33 "2022-07-10T21:16:37Z")

</div>

Amazing insights Krasimir. One of the important points that you raised in the post is “a good developer must always make informed decisions among the different options, their benefits and drawbacks” . This caught my attention and thinking from an actual developer standpoint, I tried to compare PostgreSQL vs MySQL syntax usage for day to day. Here is the link [https://tipseason.com/postgres-vs-mysql-syntax-comparision/](https://tipseason.com/postgres-vs-mysql-syntax-comparision/) . Sharing it so that developers can have a feel of how both of them look like.

---

<div class="post-metadata">

**Author:** ![Kris](https://avatars.discourse-cdn.com/v4/letter/k/82dd89/32.png) [@Kris](https://devforum.okta.com/u/Kris)\
**Post date:** [July 2, 2024, 6:18am UTC](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097/35 "2024-07-02T06:18:57Z")

</div>

Though some differences become void (over time), the overview was ok. From a java developer perspective, using JPA hibernate, how this will differ is unknown. Theory wise there could be many features, but pointless if not availed. usage is more important.

[Previous page](https://devforum.okta.com/t/mysql-vs-postgresql-choose-the-right-database-for-your-project/17097.md?page=1)
