A Byte of Coding Issue 375

A Byte of Coding Issue 375

Author

Alex Zdanov
March 27, 2024

A Byte of Coding

Hey-yo,

Are you a quick or slow pooper?

Here’s dat issue.

Made possible through generous sponsorship by:

Published: 26 March 2024

Tags: postgres, database

Vlad Mihalcea dives into how HOT updates work in postgres. We had another article on this last week (I think?), but it’s always good to read another perspective.

Some highlights:

  • HOT updates are used to make updates faster

  • can’t be used if an index column is updated

  • “Without the Heap-Only Tuple or HOT Update optimization, PostgreSQL can suffer from Write Amplification”

Published: 24 March 2024

Tags: embed, os, hubris

Cliff L. Biffle describes a bug that arose in the hubris OS from the addition of two features.

Some highlights:

  • “Hubris tasks can communicate with each other using messages in an Inter-Process Communication scheme, or IPC”

  • task packing broke assumptions in the memory allocation code

  • the fix required the memory protection algorithm to account for loaned memory across memory protection units

Published: 25 January 2024

Tags: sponsored, auth

WorkOS discusses what Directory Sync and System for Cross Identity Management are, and why they’re necessary for large organizations.

Some highlights:

  • Directory sync “automates the lifecycle management process by providing a single source of truth for identity”

  • “SCIM is an open source protocol for implementing Directory Sync”

  • includes comparison to just-in-time provisioning

Published: 21 March 2024

Tags: automation, bash, ruby

Joseph Glass elaborates on how and why it’s useful to create “shortcuts” for yourself. Not so much a deep-dive, but Joseph makes some interesting points that made me personally set up some bash aliases for commands I frequently run.

Some highlights:

  • saving yourself seconds on tasks you do 10s or 100s of times a day can have a big impact

  • includes some good inspiration for bash aliases

  • “Keep commands short”

Take control of your AWS spend and cut backup bills by 50%

As cloud adoption increases to run modernized applications, costs can quickly rise out of control. How do best-in-class companies manage their storage spend while continuing to grow the business? Clumio, a cloud-native backup solution, depends on cloud storage to run their entire business. They took a FinOps approach to optimizing their costs, and reduced their AWS dev costs by over 50%.

Thanks for your Support!

Big thanks to all of the Patreon supports and company sponsors. If you want to support the newsletter you can checkout the Patreon page. It's not necessary, but it lets me know that I'm doing a good job and that you're finding value in the content.