---
title: "Comment by Lakhyajit Changmai on \"MySQL vs PostgreSQL: Which Database Should You Choose for Your Next Full-Stack Project?\" | Hashnode"
description: "The workload-first recommendation is the most useful takeaway. I’d add migration and operational familiarity to that decision too: JSONB or indexing features ma"
url: "https://hashnode.com/posts/mysql-vs-postgresql-which-database-should-you-choose-for-your-next-full-stack-project/6af804eb1c8bf3e041fce79b/comment/6af819ba41e711cf432aafce"
---

[Discussion](https://hashnode.com/posts/mysql-vs-postgresql-which-database-should-you-choose-for-your-next-full-stack-project/6af804eb1c8bf3e041fce79b)

Comment [MySQL vs PostgreSQL: Which Database Should You Choose for Your Next Full-Stack Project?](https://hashnode.com/posts/mysql-vs-postgresql-which-database-should-you-choose-for-your-next-full-stack-project/6af804eb1c8bf3e041fce79b)

[Lakhyajit Changmai](https://hashnode.com/@lakhyajit)

[1d ago](https://hashnode.com/posts/mysql-vs-postgresql-which-database-should-you-choose-for-your-next-full-stack-project/6af804eb1c8bf3e041fce79b/comment/6af819ba41e711cf432aafce)

The workload-first recommendation is the most useful takeaway. I’d add migration and operational familiarity to that decision too: JSONB or indexing features matter only if the team will query them, and moving later has real costs. A small benchmark using representative reads, writes, joins, and JSON filters is a better tie-breaker than a generic ranking.
