We started CallFS after yet another late-night “why did the uploads vanish?” incident. Our small team had stitched together rsync, a fragile NFS mount, and an S3 bucket—none of it observable, all of it waiting to bite us.
So we wrote a single-process file service in Go that: • Speaks the S3 API (so existing tooling works). • Stores hot data on local disks for speed; cold data can sit in any S3-compatible bucket. • Exposes Prometheus metrics and JSON logs by default, because “what happened?” shouldn’t be guesswork. • Ships as a ~25 MB static binary—no external deps, MIT license.
Today it’s stable for single-node or side-by-side deployments. Clustering is on the roadmap, replication will follow, but we wanted to share the code early and hear real-world pain points. If storage glue code ever ruined your weekend, we’d love feedback and PRs.
Comments URL: https://news.ycombinator.com/item?id=44567650
Points: 24
# Comments: 3
Melden Sie sich an, um einen Kommentar hinzuzufügen
Andere Beiträge in dieser Gruppe

Article URL: https://clickhouse.com/blog/sigterm-postgres-mystery

Article URL: https://tomrenner.com/posts/llm-inevitabilism/

Article URL: https://www.ycombinator.com/companies/martin/jobs/
Article URL: https://www.nytimes.com/2025/07/08/magazine/fda-collapse-rfk-kennedy.html
Comments URL: