It’s very likely that app or database design decision you choose will become a problem before the actuall database engine itself. As others have wrote, you will not hit limitations there soon. For ecto and Saas style apps Postgres is the first choice for me there.īoth Postgres and MySQL can scale quite well given enough hardware resources. Instead of focusing on scaling I would focus on features offered, available documentation resources and compatibility. If you’re already familiar with MySQL then it’s also fine to use that instead. Personally I would recommend Postgres since IMHO it has more features to offer and good support in Ecto. If you’re trying to build a SaaS you will very likely run into a 1000 other problems before MySQL or Postgres will get in your way. Hi would suggest to stick with Postgres or MySQL unless you know why you need to choose something else. 98 - 99% of everything in my service will be reads, only a tiny fraction will be writes to the database. Perhaps some realtime data input recording would be a better case for Postgres, I think in my case MySQL is the better option. Meanwhile, MySQL is known to be faster with read-only commands. PostgreSQL is known to be faster while handling massive data sets, complicated queries, and read-write operations. So, the MySQL license is ok for me for my web project meaning the SaaS is what I am after anyway.Īlso, again, MySQL seems to be focused on web usage a lot, meaning much more reads than writes, as mentioned here: PostgreSQL vs MySQL: The Critical Differences | Xplenty The advantage of being able to embed Postgres with my app because of it’s liberal license is not important for me because it’s a web service hosted on a server and not a stand alone program. Postgres seems to need much more research and learning how to configure stuff out of the box. MySQL also seems to be better configured for common web usage out of the box. So, if MySQL can handle Uber it will be ok for me, I guess. The scaling in the future factor is a huge plus of MySQL.Īlso Uber went back to MySQL from Postgres. Thanks, I think I will go with MySQL then.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |