@fastify.dev’s logo was a lot harder to try and replicate 🤣. Might need to take a second try on that one.

It is my absolute pleasure to announce Lokalise launching an OSS support fund. Within the first cohort we are providing monthly funding to @drizzle.team , @biomejs.dev , @fastify.dev and several other projects. Special kudos to @ondrejsevcik.bsky.social for championing this idea until it happened!

This week we launched our next-gen API built on @fastify.dev, fully documented with OpenAPI, and with a modular design, which made it easy to implement some new Fleet Telemetry features too. It wasn't the smoothest launch I've done... teslemetry.com/blog/move-fa...

Move fast, break things

Introducing the next-gen API and more flexible Fleet Telemetry

teslemetry.com

I just copy pasted a documentation page into @github.com CoPilot with Claude 3.5, and it wrote all the @fastify.dev / OpenAPI schema for me. The time I save using CoPilot far exceeds its cost many times over.

Here we are! Ask anything you need about building @nodejs.org APIs.

Yes! HAProxy! Love that thing. I saw so many issues of people “doing it wrong” that I put a guide in to @fastify.dev’s documentation that specifically uses HAProxy, because that’s what people should be using. Not pm2 or whatever other nonsense they’ve cooked up themselves

Jake Gold@jacob.gold · 2y ago

An unordered / non-exhaustive list of things that helped scale Bluesky's infra efficiently: + Exiting the cloud (colocation) + HAProxy w/many Node backends + Go w/clever code + ScyllaDB + SQLite w/per user databases + Redis w/many instances + AMD servers w/many cores + Purchasing bandwidth directly