• "The original idea of relational databases was that they would be queried directly from the client"
• "The success of GraphQL shows that these pains are real and that people really do want to issue rich queries directly from the client"
• "Firebase was able to succesfully compete by recognizing that the current division of database + sql + orm + application-layer is a historical accident and can be dramatically simplified." To summarize:

Design flaws in the SQL language resulted in a language with no library ecosystem and a burdensome spec which limits innovation.
Additional design flaws in SQL database interfaces resulted in moving as much logic as possible to the application layer and limiting the use of the most valuable features of the database.
It's probably too late to fix either of these.

• More signals on HN homepage that sqlite might be gaining popularity
• "I implemented a virtual file system that fetches chunks of the database with HTTP Range requests when SQLite tries to read from the filesystem"

• More sqlite love
• "I have run SQLite as a web application database with thousands concurrent writes every second, coming from different HTTP requests, without any delays or issues"
• "the AUTOINCREMENT command is different, and also that SQLite uses a dynamically and weakly typed SQL syntax that does not guarantee the domain integrity"
• "if a INTEGER PRIMARY KEY column is not explicitly given a value, then it will be filled automatically with an unused integer"

• Correctness, readability, then optimization.
• Make your Haystacks as small as possible before searching for your needles
• Prefer = to LIKE
• Avoid bookending wildcards in WHERE statements

• "It’s astoundingly cheap. Typical costs are only about $1 per month."
• "Exciting features coming including replication to read-only replicas. This will give you the ability to run local copies of your database at the edge to deliver requests instantly."