@fastify.dev
Pinned
fastify.dev
@fastify.dev
· Nov 11
Here we are! Ask anything you need about building @nodejs.org APIs.
Reposted
@fastify.dev’s logo was a lot harder to try and replicate 🤣. Might need to take a second try on that one.
January 29, 2025 at 8:26 PM
@fastify.dev’s logo was a lot harder to try and replicate 🤣. Might need to take a second try on that one.
Reposted
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!
Special kudos to @ondrejsevcik.bsky.social for championing this idea until it happened!
January 23, 2025 at 3:10 PM
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!
Special kudos to @ondrejsevcik.bsky.social for championing this idea until it happened!
Reposted
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...
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
January 17, 2025 at 1:16 PM
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...
It wasn't the smoothest launch I've done...
teslemetry.com/blog/move-fa...
Reposted
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.
The time I save using CoPilot far exceeds its cost many times over.
December 31, 2024 at 5:18 AM
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.
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.
November 11, 2024 at 3:35 PM
Here we are! Ask anything you need about building @nodejs.org APIs.
Reposted
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
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
+ 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
November 11, 2024 at 2:50 PM
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