Hollow Byte @stacktrackguy

22 • SWE • Databases • Low-Level stuff addict • Backend Systems Joined September 2025

Tweets

222
Followers

63
Following

154
Likes

381

Hollow Byte @stacktrackguy

3 days ago

Most thinks consistency is binary, either your DB is “consistent” or it isn’t. In reality: Leaderless Replication (Dynamo/Cassandra) let you write anywhere → great for uptime + latency But now your reads can conflict For fixing, choose your tradeoff : last-write-wins (fast,…

0 0 4 132 0

Hollow Byte @stacktrackguy

3 days ago

Most systems don’t crash because of “bad code.” They crash because of bad data. One corrupt record and suddenly queries are garbage Half a write? Now you’re in inconsistent state hell Two systems disagree on the “truth”? Phantom bugs forever This is why stuff like Kafka…

0 0 5 164 1

Hollow Byte @stacktrackguy

4 days ago

I Love DATABASES. Been nerding out on replication models this week. Single-leader replication: one node takes writes, others just copy simple + consistent downside: leader becomes the bottleneck, failover hurts Multi-leader replication: multiple nodes can accept writes great…

0 0 5 158 0

Hollow Byte @stacktrackguy

4 days ago

I love DATABASES. I was reading this week about how Postgres connection pooling can quietly kill performance. Too many idle connections pile up -> memory bloat + file descriptors eaten -> Postgres ends up spending more time handling connections than serving queries. Simple…

1 0 5 121 1

Hollow Byte @stacktrackguy

4 days ago

Was working on a side project in Go the other night and ran into a stupid crash. No clue where it was coming from. Instead of scrolling through the code, forced myself to slow down and stick to a process: cut code in half until I isolated it (binary search style) reproduced it…