If you are looking for all the bells and whistles in a database then your answer is going to be hands down Postgres. In terms of features it really depends on what you need. Winner: Aurora MySQL Features – Aurora MySQL vs Postgres Features – Aurora MySQL vs Postgres ![]() Having said that in all other cases and in intense load they both score equally in cost. The instance size only supported in Aurora MySQL is db.t3.small. If you try to go with Aurora Postgres then you need to go to the second tier. Let me be more specific, if you require a database that’s going to be smaller than 2GB in size then only Aurora MySQL offers that option at the time of this writing. However there’s one case where Aurora MySQL is cheaper than Aurora Postgres and this is for very small instances. After we have deployed both instances in many different scenarios I can safely say for the most part they both cost approximately the same thing. This is the most important question that I get asked when I try to compare the two. Cost – Aurora MySQL vs Postgres Cost – Aurora MySQL vs PostgresĬost, cost and cost. I will go over each point on their main differences to help you decide which is good for you. I have personally used both backends in some of my projects and have quite a bit of experience on knowing their differences.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |