#databases — Public Fediverse posts

River Engineering writer Vivian Mathews retells their company's 16-month-long saga to replace an aging accounting ledger system with a refactored, highly optimized new version. They go through the nitty-gritty of how they successfully pulled-off a zero-downtime migration including code examples and key takeaways for the TL;DR crowd.

"We replaced our ledger with two functions"

https://river.com/content/we-replaced-our-ledger-with-two-functions

#programming #databases #accounting #ledgers #optimization #refactoring #migration #testing

River Engineering writer Vivian Mathews retells their company's 16-month-long saga to replace an aging accounting ledger system with a refactored, highly optimized new version. They go through the nitty-gritty of how they successfully pulled-off a zero-downtime migration including code examples and key takeaways for the TL;DR crowd.

"We replaced our ledger with two functions"

https://river.com/content/we-replaced-our-ledger-with-two-functions

#programming #databases #accounting #ledgers #optimization #refactoring #migration #testing

River Engineering writer Vivian Mathews retells their company's 16-month-long saga to replace an aging accounting ledger system with a refactored, highly optimized new version. They go through the nitty-gritty of how they successfully pulled-off a zero-downtime migration including code examples and key takeaways for the TL;DR crowd.

"We replaced our ledger with two functions"

https://river.com/content/we-replaced-our-ledger-with-two-functions

#programming #databases #accounting #ledgers #optimization #refactoring #migration #testing

River Engineering writer Vivian Mathews retells their company's 16-month-long saga to replace an aging accounting ledger system with a refactored, highly optimized new version. They go through the nitty-gritty of how they successfully pulled-off a zero-downtime migration including code examples and key takeaways for the TL;DR crowd.

"We replaced our ledger with two functions"

https://river.com/content/we-replaced-our-ledger-with-two-functions

#programming #databases #accounting #ledgers #optimization #refactoring #migration #testing

River Engineering writer Vivian Mathews retells their company's 16-month-long saga to replace an aging accounting ledger system with a refactored, highly optimized new version. They go through the nitty-gritty of how they successfully pulled-off a zero-downtime migration including code examples and key takeaways for the TL;DR crowd.

"We replaced our ledger with two functions"

https://river.com/content/we-replaced-our-ledger-with-two-functions

#programming #databases #accounting #ledgers #optimization #refactoring #migration #testing

New things for regular expressions in PostgreSQL (pg_tre and pg_re2) via @fanf https://lobste.rs/s/b53fwj #databases
https://www.depesz.com/2026/08/25/new-things-for-regular-expressions-in-postgresql-pg_tre-and-pg_re2/

New things for regular expressions in PostgreSQL (pg_tre and pg_re2) via @fanf https://lobste.rs/s/b53fwj #databases
https://www.depesz.com/2026/08/25/new-things-for-regular-expressions-in-postgresql-pg_tre-and-pg_re2/

New things for regular expressions in PostgreSQL (pg_tre and pg_re2) via @fanf https://lobste.rs/s/b53fwj #databases
https://www.depesz.com/2026/08/25/new-things-for-regular-expressions-in-postgresql-pg_tre-and-pg_re2/

New things for regular expressions in PostgreSQL (pg_tre and pg_re2) via @fanf https://lobste.rs/s/b53fwj #databases
https://www.depesz.com/2026/08/25/new-things-for-regular-expressions-in-postgresql-pg_tre-and-pg_re2/

New things for regular expressions in PostgreSQL (pg_tre and pg_re2) via @fanf https://lobste.rs/s/b53fwj #databases
https://www.depesz.com/2026/08/25/new-things-for-regular-expressions-in-postgresql-pg_tre-and-pg_re2/

Read your own writes, off the primary via @caius https://lobste.rs/s/vq68cd #databases
https://boringsql.com/posts/read-your-own-writes/

Read your own writes, off the primary via @caius https://lobste.rs/s/vq68cd #databases
https://boringsql.com/posts/read-your-own-writes/

Read your own writes, off the primary via @caius https://lobste.rs/s/vq68cd #databases
https://boringsql.com/posts/read-your-own-writes/

Read your own writes, off the primary via @caius https://lobste.rs/s/vq68cd #databases
https://boringsql.com/posts/read-your-own-writes/

Read your own writes, off the primary via @caius https://lobste.rs/s/vq68cd #databases
https://boringsql.com/posts/read-your-own-writes/

Please stop calling databases CP or AP (2015)

https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html

Comments: https://news.ycombinator.com/item?id=49521490

#HackerNews #databases #CP #AP #dataarchitecture #datastorage #technology

Please stop calling databases CP or AP (2015)

https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html

Comments: https://news.ycombinator.com/item?id=49521490

#HackerNews #databases #CP #AP #dataarchitecture #datastorage #technology

Please stop calling databases CP or AP (2015)

https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html

Comments: https://news.ycombinator.com/item?id=49521490

#HackerNews #databases #CP #AP #dataarchitecture #datastorage #technology

Please stop calling databases CP or AP (2015)

https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html

Comments: https://news.ycombinator.com/item?id=49521490

#HackerNews #databases #CP #AP #dataarchitecture #datastorage #technology

Please stop calling databases CP or AP (2015)

https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html

Comments: https://news.ycombinator.com/item?id=49521490

#HackerNews #databases #CP #AP #dataarchitecture #datastorage #technology

AWS: DuckDB will provide 'connective tissue' across the data estate https://www.theregister.com/databases/2026/09/01/aws-duckdb-will-provide-connective-tissue-across-the-data-estate/5293304 #theRegister #Databases

AWS: DuckDB will provide 'connective tissue' across the data estate https://www.theregister.com/databases/2026/09/01/aws-duckdb-will-provide-connective-tissue-across-the-data-estate/5293304 #theRegister #Databases

AWS: DuckDB will provide 'connective tissue' across the data estate https://www.theregister.com/databases/2026/09/01/aws-duckdb-will-provide-connective-tissue-across-the-data-estate/5293304 #theRegister #Databases

Condensing the classification found in "Still Building the Memex" (Davies 2010), I'd be comfortable dividing personal knowledge base structural frameworks into two categories: Link-based and Category-based.

Tree-structured and graph-structured organizers are link-based. Tag-structured organizers are category-based. Because select and join are key-matching operations, relational #databases are also category-based.

For the link-based systems the primitive operation is to follow a link. For the category-based systems the primitive operation is to separate a collection of data into items belonging to a particular category and items not belonging to the category.

(Thread continues... 🧵)

Condensing the classification found in "Still Building the Memex" (Davies 2010), I'd be comfortable dividing personal knowledge base structural frameworks into two categories: Link-based and Category-based.

Tree-structured and graph-structured organizers are link-based. Tag-structured organizers are category-based. Because select and join are key-matching operations, relational #databases are also category-based.

For the link-based systems the primitive operation is to follow a link. For the category-based systems the primitive operation is to separate a collection of data into items belonging to a particular category and items not belonging to the category.

(Thread continues... 🧵)

Condensing the classification found in "Still Building the Memex" (Davies 2010), I'd be comfortable dividing personal knowledge base structural frameworks into two categories: Link-based and Category-based.

Tree-structured and graph-structured organizers are link-based. Tag-structured organizers are category-based. Because select and join are key-matching operations, relational #databases are also category-based.

For the link-based systems the primitive operation is to follow a link. For the category-based systems the primitive operation is to separate a collection of data into items belonging to a particular category and items not belonging to the category.

(Thread continues... 🧵)

Condensing the classification found in "Still Building the Memex" (Davies 2010), I'd be comfortable dividing personal knowledge base structural frameworks into two categories: Link-based and Category-based.

Tree-structured and graph-structured organizers are link-based. Tag-structured organizers are category-based. Because select and join are key-matching operations, relational #databases are also category-based.

For the link-based systems the primitive operation is to follow a link. For the category-based systems the primitive operation is to separate a collection of data into items belonging to a particular category and items not belonging to the category.

(Thread continues... 🧵)

Condensing the classification found in "Still Building the Memex" (Davies 2010), I'd be comfortable dividing personal knowledge base structural frameworks into two categories: Link-based and Category-based.

Tree-structured and graph-structured organizers are link-based. Tag-structured organizers are category-based. Because select and join are key-matching operations, relational #databases are also category-based.

For the link-based systems the primitive operation is to follow a link. For the category-based systems the primitive operation is to separate a collection of data into items belonging to a particular category and items not belonging to the category.

(Thread continues... 🧵)