Node.js Design Patterns (the book 📙) is currently #9 in the WebServices category and #15 in the JavaScript category on Amazon!. I am really proud of these results! 🤩. Thanks to everyone who has kindly left us a review ❤️.

RT @matteocollina: 🧵 At JSNation, I showed graphs that honestly left me speechless about Node.js upgrade patterns. Let me break down why I'….

RT @astuyve: NEW: AWS is rolling out a new free tier beginning July 15th!!. New accounts get $100 in credits to start and can earn $100 exp….

Just made my first contribution to #Nextjs!. It’s a small docs fix, but hopefully it’ll save someone a bit of time down the road: Big or small, every contribution counts. that’s the power of open source! 💪. #Nextjs #OpenSource #DevLife #JavaScript.

PS: Recognize the meme that inspired our episode art? 😏. Bonus points if you spot it 🙃. #AWS #AuroraDSQL #ServerlessSQL #PostgreSQL #CloudComputing #Fastify #DrizzleORM #Lambda #DevOps #MultiRegion #CostOptimization.

🎧 Watch the full episode:. ▶️ Let us know if you're trying DSQL. What's your experience so far? 🤨.

🔹 Is it right for you?. ✅ Great for greenfield and serverless-first projects.⚠️ Avoid if you rely on foreign keys, triggers, or complex extensions. or if the migration cost might be too high!.

🔹 Cost in focus:. DSQL uses DPUs (Distributed Processing Units), but billing is… a bit fuzzy 😅. CloudWatch helps, and @marcbowes has a great cost estimator tool 💸.

🔹 We built & tested a real app:. ➡️ Lambda + Api Gateway.➡️ Fastify + Drizzle + CDK.➡️ k6 load testing.➡️ AWS X-Ray tracing. Full code + infra:

🔹 But it’s not perfect…. No foreign keys, special async-only indexes, no stored procs, no support for the SERIAL type. We cover what this means for real-world apps and if you are using various Postgres tools or ORMs.

🔹 True serverless SQL?. DSQL delivers active-active multi-region setup with 99.999% availability, zero patching, and no manual sharding. DBA nightmares = gone (almost).

🚀 New AWS Bites episode!. We tried Amazon #DSQL so you don’t have to (but you might want to) 👀. Luciano and Eoin put Aurora DSQL through its paces in #AWS Bites #Podcast Episode 145. 🧵 Here’s what we found:

Credit to Joe on BlueSky for reporting this!

Using `xxd` instead, it's clear that echo only adds a `\n` at the end:. ```.echo -n "banana" | xxd.00000000: 6261 6e61 6e61              banana.```.VS. ```.echo "banana" | xxd.00000000: 6261 6e61 6e61 0a            banana. ```.

❌ ERRATA:. It turns out that NUL byte doesn't really exist in the input. it's just an artefact of hexdump (or I should say "it's me, I can't read hexdump output")!.

Hope this saves someone else 20 minutes of confused debugging 😅. And if not… maybe you picked up a couple of handy shell tricks along the way 🐚💡. #NodeJS #JavaScript #Hashing #Crypto #WebDev #Debugging #CLI #DevTips #LearnByDoing #TIL.

🔍 Lesson learned:.Invisible bytes are still bytes. They might not be printable, but they are part of the input. And when hashing, every byte matters. Even a single-byte difference gives you a completely different result. That’s not a bug, that’s the whole point!.

Using "-n" with echo keeps the input clean, no extra bytes added!. Now with the corrected command:. $ echo -n "banana" | sha1.250e77f12a5ab6972a0895d290c4792f0a326ea8.💥 Same hash as Node.js!. Mystery solved.

Let’s look at the bytes 👇. $ echo "banana" | hexdump.0000000 6162 616e 616e 000a ← includes 00 (NUL) and 0a (newline).Compare with:. $ echo -n "banana" | hexdump. 0000000 6162 616e 616e ← clean input!.

Turns out, echo adds a few sneaky bytes to your input: a NUL byte and a newline (\n). That tiny difference is enough to throw off your hash completely. Because hashing is exact. that’s the whole point!.

Node.js gave me this hash:. 250e77f12a5ab6972a0895d290c4792f0a326ea8. But the terminal?. 8a1aaf746ada2a80fab03a58c91575ffe82885ac. Same string. Different hashes. What gives? 🥸.