Hacker News with Generative AI: Database Design

The principles of database design, or, the Truth is out there (ebellani.github.io)
Every software project needs to represent the reality of the business he is embedded in. The way we can represent reality as limited rational beings is through propositions, i.e, declarative statements that affirm or deny something about reality. When a collection of such propositions is stored in a computer system, we call it a database.

Database Design, Software Development, Philosophy

119 points by b-man 5 days ago | 118 comments

Vertical Sharding Sucks (pgdog.dev)
Vertical sharding, sometimes called functional sharding, takes tables out of your main database and puts them somewhere else. Most of the time, it’s another Postgres database. This reduces load on the main DB and gives your app some breathing room to grow.

Database Design, Performance Optimization, Scaling, Postgres

20 points by samokhvalov 42 days ago | 13 comments

Why Vector DBs Are the Wrong Abstraction – and What We Built Instead (topk.io)
We’ve spent the last three years building the most popular vector database on the market. In that time we realized that a database built around vectors as a primary key is simply the wrong abstraction, creating an unnecessary obstacle for users in production.

Vector Databases, Database Design, Artificial Intelligence

23 points by Void_ 73 days ago | 8 comments

Scrap Your ORM–Replacing Your ORM with Relational Algebra (youtube.com)

Database Design, Relational Algebra, ORM, Software Development

8 points by todsacerdoti 90 days ago | 0 comments

How can you represent inheritance in a database? (2010) (stackoverflow.com)
I'm thinking about how to represent a complex structure in a SQL Server database.

Database Design, Inheritance, SQL Server

35 points by stefankuehnel 159 days ago | 22 comments

Logical vs. Physical Data Types (spiraldb.com)

Database Design, Data Types

33 points by gatesn 211 days ago | 0 comments

Code in Database vs. Code in Application (brandur.org)
A perennial question in the database world: should you prefer to keep application logic closer to the database itself, in stored procedures and triggers, or above the database in your application code?

Database Design, Programming, Software Development

14 points by timokoesters 233 days ago | 8 comments

ChartDB – Free and open source, database design editor (chartdb.io)

Database Design, Open Source, Tools, Software

259 points by nikolay 269 days ago | 38 comments

Show HN: Visualize database schemas with a single query (github.com/chartdb)

Database Design, Visualization, Tools, Software, Data

227 points by Jonathanfishner 272 days ago | 64 comments

Database Design for Google Calendar: A Tutorial (databasedesignbook.com)

Database Design, Google Calendar, Tutorials

293 points by fagnerbrack 305 days ago | 100 comments

Path Dependence in Relational Design (minimalmodeling.substack.com)

Database Design, Relational Databases, Software Development

10 points by thunderbong 320 days ago | 0 comments

Why Choose ULIDs over Traditional UUIDs or IDs for Database Identification? (sotergreco.com)