Join us

Deeper theories of program design

Deeper theories of program design

A sharp teardown of Windows vs. Unix file deletion semantics lands on this: Windows leans on read-write locks; Unix rolls with a looser, non-blocking vibe—more like weakly-isolated DB transactions. It trades consistency for concurrency, dodging locks even if it means the rules get fuzzy.

The post zooms out, too. Filesystems like FxFS and ZFS are now shipping with transactional guts. Meanwhile, databases—Aurora DSQL, Spanner, TigerBeetle—are pushing default isolation toward Serializable or higher.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

By subscribing, you share your email with @faun and accept our Terms & Privacy. Unsubscribe anytime.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start blogging about your favorite technologies, reach more readers and earn rewards!

Join other developers and claim your FAUN.dev account now!

Avatar

The FAUN

@faun
A worldwide community of developers and DevOps enthusiasts!
Developer Influence
3k

Influence

302k

Total Hits

1

Posts