undefined | Better HN

0 pointsTX81Z2y ago0 comments

I think that’s part of why I’m having trouble with this framing - it’s treating CRUD as the entire universe of why you’d need to connect to a database.

Some of us do very intense compute in very large datasets, and ORM are not capable in those tasks. At all.

0 comments

hot_gril2y ago

Doesn't even have to get very intense. A simple timeseries schema gets slow/annoying quickly with an ORM.

TX81ZOP2y ago

I think for a lot of things an ORM is “good” at, you could likely just have a bunch of static JSON files and retrieve them from disk with zero practical difference.

I just can’t wrap my head around why you even *need* a database in those cases.

hot_gril2y ago

Honestly I wouldn't deal with JSON files on disk except as a last resort. Aside from convenience, you need a DB for transactional reads/writes. But you don't need an ORM for that anymore because Postgres and MySQL have json/jsonb types.

j / k navigate · click thread line to collapse

0 pointsTX81Z2y ago0 comments

I think that’s part of why I’m having trouble with this framing - it’s treating CRUD as the entire universe of why you’d need to connect to a database.

Some of us do very intense compute in very large datasets, and ORM are not capable in those tasks. At all.

0 comments

hot_gril2y ago

Doesn't even have to get very intense. A simple timeseries schema gets slow/annoying quickly with an ORM.

TX81ZOP2y ago

I think for a lot of things an ORM is “good” at, you could likely just have a bunch of static JSON files and retrieve them from disk with zero practical difference.

I just can’t wrap my head around why you even *need* a database in those cases.

hot_gril2y ago

j / k navigate · click thread line to collapse