4 ms·
There was LAMP and then MERN and MEAN etc. and then there was Postgres. Its not quite visible yet, but all this progres by postgres (excuse the pun) on making
by openrisk 2y ago
There was LAMP and then MERN and MEAN etc. and then there was Postgres.
Its not quite visible yet, but all this progres by postgres (excuse the pun) on making JSON more deeply integrated with relational principles will surely at some point enable a new paradigm, at least for full stack web frameworks?
- winrid 2y agoThe problem with postgres's JSON support is it leads to last write win race conditions compared to actual document stores. Once they can support operations like incrementing a number while someone else updates another field, without locking the row, then maybe. I don't think you'll see a paradigm shift. You'll just see people using other documents stores less.
- sgarland 2y agoWe’re already in a new paradigm, one in which web devs are abandoning referential integrity guarantees in favor of not having to think about data modeling. I’d say they’re then surprised when their DB calls are slow (nothing to do with referential integrity, just the TOAST/DETOAST overhead), but since they also haven’t experienced how fast a DB with local disks and good data locality can be, they have no idea.
- pnt12 2y agoCan you elaborate on what's TOAST/DETOAST?
- davidrowley 2y agoThe Oversized-Attribute Storage Technique. https://www.postgresql.org/docs/17/storage-toast.html https://www.postgresql.org/docs/17/storage-toast.html