Best Products
Launches
Launch archive
Most-loved launches by the community
Launch Guide
Checklists and pro tips for launching
News
Newsletter
The best of Product Hunt, every day
Stories
Tech news, interviews, and tips from makers
Changelog
New Product Hunt features and releases
Forums
Forums
Ask questions, find support, and connect
Kitty Points Leaderboard
The highest scoring community members
Streaks
The most active community members
Events
Meet others online and in-person
Advertise
Subscribe
Sign in
Clear text
recent
p/self-promotion
by
pxyedge
•
5d ago
How do you handle IP bans when scraping at scale?
... When evaluating providers, look at: geographic diversity (city-level targeting is a game-changer for local market research), ASN distribution, and whether they actually vet their residential sources. Cheap proxies are expensive in wasted engineering hours. 3. Configure
concurrency
thoughtfully Blasting 1000
concurrent
0
2
p/self-promotion
by
Anna Prescott
•
2mo ago
How I fixed DeepSeek/Qwen 429 errors with a custom API gateway
... solve this for my own development workflows, I ve been building a high-speed API relay station. It aggregates models like DeepSeek-V4, Qwen 3.7, GLM 5.1, Kimi 2.6, and Minimax-M2.7, with a primary focus on
concurrency
and stability. Here is a quick look at the infrastructure under the hood: Routing & Latency: Deployed on optimized acceleration routes (Singapore/US West). The TTFT (Time-To-First-Token) is nearly instant for stream responses. Failover Stability: Built-in enterprise load ... ... word for it, I d love for you to run your own automated benchmarks (llm-benchmark, multi-threading, etc.) and tear it apart. You can test the sandbox here: [Link: model.usddd.org ] To help the PH community test the
concurrency
0
1
p/votap
by
Alexandr Cizek
•
3mo ago
I just hit the kill switch on my own app…
... kill switch on my own app And honestly every app should have this. Right after pushing the new update, I wanted to test it like a normal user. Very soon I spotted a bug. Because of a
concurrency
issue, some users who already had a username assigned could sometimes see the picker again and sometimes not. That s the worst kind of bug. It works. Until it doesn t. Completely random. Pure luck depending on what runs first ... ... into maintenance mode . Everyone sees a simple screen, no interaction, until it s fixed. Not fun but way better than letting users run into broken logic. I always knew I d mess something up eventually This time it was
concurrency
33
48
p/self-promotion
by
Alexandr Cizek
•
3mo ago
I just hit the kill switch on my own app…
... kill switch on my own app And honestly every app should have this. Right after pushing the new update, I wanted to test it like a normal user. Very soon I spotted a bug. Because of a
concurrency
issue, some users who already had a username assigned could sometimes see the picker again and sometimes not. That s the worst kind of bug. It works. Until it doesn t. Completely random. Pure luck depending on what runs first ... ... into maintenance mode . Everyone sees a simple screen, no interaction, until it s fixed. Not fun but way better than letting users run into broken logic. I always knew I d mess something up eventually This time it was
concurrency
0
5
p/self-promotion
by
Aleksei Aleinikov
•
11mo ago
Scaling with Go in 2025 - 7 Battle-Tested Concurrency Patterns
...
Concurrency
is a power tool and in Go, it s one of the cleanest, fastest ways to scale. But how do you use it right in 2025? In this deep-dive, I ll walk you through 7 proven patterns to make your Go programs faster and safer: Future / Promise Generator Pipeline Fan-out & Fan-in Semaphore Worker Pool Robust error aggregation Each pattern comes with fresh, clean examples and concise explanations. Bookmark it as your quick reference for production ... ... grade Go
concurrency
0
1
Subscribe
Sign in