I created an RDS postgres database with the lowest settings - literally free tier on everything, but apparently I don't qualify for that anymore.
I was never able to figure out how to create a table, put data into it, or connect to it.
However, I was charged $10 a day for a few days, so I killed it and won't be going back. I've had multiple similar experiences with AWS and I never get an explanation for the charged from AWS.
Is there any explanation for this? I use heroku and firebase and never have nearly as much difficulty using those and I've never had a billing issue or random charges.
Update:Here is a detail for the billing. How did this happen?
Update 2:
After feedback here that the costs came from the storage type, I went back and looked at the creation process to see what happened. In selecting the "Easy Create" process for a postgres RDS database, the more expensive storage type was the "default". That's pretty upsetting to me and I really wish that there was something that told you the project cost prior to activation, but at least I figured out what happened. I'm gonna recreate and see if I can't get it cheaper.
Thanks for the help.
Why Postgres RDS didn't work for us
Amazon RDS Extended Support for Postgres 11
database - AWS RDS MySql or Postgres - performance wise and cost wise? - Stack Overflow
Cost wise to run Postgres is it EC2 < Runner < RDS?
Videos
This can be very broad and may be opinionated , I would try to keep it short as i read it somewhere:
MySQL would be very good for any CMS Site as it works very well with it and MyISAM tables are quite nice here.
From What I read where PostgreSQL does better than MySQL:
- Multi-application databases
- Advanced data modelling
What Advance Data Modelling means is that PostgreSQL is far more mature at doing complex data modelling than MySQL is. It has a very mature extensible type system, a wide range of procedural languages, and a great deal of flexibility in how these languages can be plugged into existing queries.
If that wasn't enough, the fact is that you can essentially build your data model in PostgreSQL based not only on what information you are storing but what information is commonly derived from what you are storing. This makes things like not-first-normal-form actually sane to use where they are needed. Add collections and multiple inheritance in table structure and you have a very sophisticated data modelling platform, this blog would help you understand it better.
Besides the content management system market, MySQL's other major market is in applications where data is not expected to be exposed to more than one writing application at a time. This leads to a significant difference in handling data validation, etc.
In PostgreSQL validation is always equally strict. If the app expects special error treatment it had better call functions or casts to handle this explicitly.
MySQL however places the application in charge of defining the data validation rules.So while PostgreSQL allows the relational and object-relational interface to serve as a public API, it is essentially intended largely to be a private API for applications in MySQL. This is a huge difference and not readily understood by many people trying to make the choice. This leads to major differences in application design.
MySQL is a data storage and reporting solution for your application. PostgreSQL is a data centralization, modelling, and reporting solution for your organization. The two are remarkably different.
Now coming to Second Question based on pricing as you can see from MySQL Pricing Page and PostgreSQL Pricing Page MySQL is bit cheaper than PostgrSQL , reading on the answer you can make informed decision what would be best for you.
Hope this Helps!
I'm gonna offer you a 3rd option: Aurora - try it. It's cheaper than those 2 and is MySQL compatible. This article may be of help to you when deciding.
For simple blog-like thingie I'd go with MySQL (or Aurora MySQL compatible version) For data-critical and highly relational solutions I might also consider Postgres (Aurora)