This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
The 500MB Club Challenge
2 CPUs. 500MB RAM. One real Pi. Prove your language.
Most backend benchmarks run on generous cloud boxes nobody deploys to. This one doesn't: a write-heavy telemetry service (GPS/battery/accel data) has to run — LB, 3 API replicas, storage — inside 2 CPUs and 500MB RAM total, on a real Raspberry Pi. Open, language-agnostic: fork it, implement the API, ship a Docker image, submit a PR. Scored on efficiency, capacity, tail latency, resilience, stability. Sponsored by Ardan Labs, JetBrains, GopherCon Latam. Deadline: July 26.
Hey! I built this because every backend benchmark I could find ran on
hardware nobody actually ships services to — 4, 8, 16 vCPUs, gigabytes of
RAM. That's not what edge or cost-constrained deployments look like, and
it hides exactly the stuff I care about as a backend engineer: how a
runtime behaves when it doesn't have room to hide its mistakes.
So I put the whole stack — load balancer, 3 API replicas, storage — on a
single Raspberry Pi with a hard 2 CPU / 500MB ceiling, and picked a domain
that's realistically annoying: ingesting GPS/battery/accelerometer data
from thousands of couriers in real time, the kind of write-heavy,
tail-latency-sensitive workload that sits behind any delivery or mobility
app's live map.
Anyone can submit in any language — Go, Rust, Zig, Node, Python, Java,
whatever you want to prove a point with. The repo has the OpenAPI
contract, the load scripts, and the full scoring breakdown.
Huge thanks to Ardan Labs, JetBrains, and GopherCon Latam for sponsoring
prizes. Deadline is July 26 — if you don't have time to build something,
an upvote or a share to someone who'd enjoy this goes a long way. Happy to
answer anything about the scoring, the hardware setup, or why I picked
this domain.
About The 500MB Club Challenge on Product Hunt
“2 CPUs. 500MB RAM. One real Pi. Prove your language.”
The 500MB Club Challenge was submitted on Product Hunt and earned 5 upvotes and 7 comments, placing #74 on the daily leaderboard. Most backend benchmarks run on generous cloud boxes nobody deploys to. This one doesn't: a write-heavy telemetry service (GPS/battery/accel data) has to run — LB, 3 API replicas, storage — inside 2 CPUs and 500MB RAM total, on a real Raspberry Pi. Open, language-agnostic: fork it, implement the API, ship a Docker image, submit a PR. Scored on efficiency, capacity, tail latency, resilience, stability. Sponsored by Ardan Labs, JetBrains, GopherCon Latam. Deadline: July 26.
On the analytics side, The 500MB Club Challenge competes within Open Source, Developer Tools and GitHub — topics that collectively have 625.3k followers on Product Hunt. The dashboard above tracks how The 500MB Club Challenge performed against the three products that launched closest to it on the same day.
Who hunted The 500MB Club Challenge?
The 500MB Club Challenge was hunted by Carlos Henrique Guardão Gandarez. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of The 500MB Club Challenge including community comment highlights and product details, visit the product overview.
Carlos Henrique Guardão Gandarez