Amazon RDS VS EdgeDB

Database configuration - we had to modify the database configuration. This is very difficult in various database providers (like RDS) and may even not be possible. This is also not very uniform between various DB engines (like PostgreSQL and MySQL). - Source: dev.to / about 1 month ago

Amazon Database Migration Service might initially seem like a perfect tool for a smooth and straightforward migration to RDS. However, our overall experience using it turned out to be closer to an open beta product rather than a production-ready tool for dealing with a critical asset of any company, which is its data. Nevertheless, with the extra adjustments, we made it work for almost all our needs. - Source: dev.to / about 2 months ago

RDS - 750 hours per month of db.t2.micro, db.t3.micro, or db.t4g.micro, 20GB of General Purpose (SSD) storage, 20GB of storage backups. - Source: dev.to / 3 months ago

It's easy to get "database managers" and "managed databases" confused, for obvious reasons. Managed databases are a different product to database managers entirely: they are a service that hosts and maintains your database servers for you, so that you only have to worry about the data inside them. Managed databases are a great way to outsource some of your infrastructure overhead if you don't want to host database... - Source: dev.to / 3 months ago

The app can use a local PostgreSQL and has no issues using a cloud service like Amazon RDS. - Source: dev.to / 5 months ago

A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / 8 months ago

See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / 8 months ago

>relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all intended readabilty when you have SELECT col1, col2 FROM (SELECT * FROM ... WHERE 1=0 AND ... Which is what edgeDB is trying to solve. [0]https://edgedb.com/. - Source: Hacker News / 12 months ago

You have to do your own optimiser to avoid, for instance, the N+1 query problem. (Just Google that, plenty of explanations around.) Many GraphQL frameworks have a “naive” subquery implementation that performs N individual subqueries. You either have to override this for each parent/child pairing, or bolt something on the back to delay all the “SELECT * FROM tbl_subquery WHERE id = ?” operations and convert them... - Source: Hacker News / almost 2 years ago