nowfound

Alternatives

Products that do what Hyper Fetch does

Framework for data exchange, async state management and more

  1. 1

    Build data-driven React applications with GraphQL and Relay

    2017

  2. 2

    Asynchronous backlog grooming via Slack task-based surveys

    2019

  3. 3
    Reshuffle173

    The place to share and find live open source code in seconds

    2019

  4. 4RI
  5. 5RR
  6. 6ER

    2017 · github.com

  7. 7FD
  8. 8RF
  9. 9SA

    Last night, while trying to figure out the best way to implement caching in my app, I had an idea for a dirt-simple caching system based on a dependency graph. The premise I started with is that one of the hardest things to manage in a cache is dependencies between entities. In order to cache items effectively, you inevitably have to duplicate "child" data inside of "parent" entries. Then, when a child is changed, you have to invalidate the child and its parents, and its parents' parents, and so on. To try to help this, I hacked together a simple Node.js library called Stash, which models…

    2012

  10. 10IM

    I built this library because I kept rewriting the same fetch wrapper for every project. Each time, I needed the same core features: - Make fetch throw errors to integrate smoothly with libraries like TanStack Query - Add sensible defaults to the Fetch API, like a base URL and authentication headers - Validate responses for type safety when OpenAPI isn’t an option I also wanted the library to feel exactly like using fetch — no new API to learn, and no extra friction for my teammates. While there are other great options out there, I found many were either too rigid or too bulky. Doesn’t it…

    2025 · github.com

  11. 11SA

    Hi HN, we’re Jessie and Eric. We’ve been baking away at Cakework (https://www.cakework.com/), which is a way to build async backends without needing to manage cloud infrastructure. Cakework is for operations that take time or more compute, like file processing, report generation, or machine learning. Devs write backends as Python functions and deploy them with our CLI. They use our client SDKs to make requests, get status, and get processing results. Each request runs with its own CPU and memory parameters in its own microVM, with no timeouts. Devs can query for failures and…

    2023 · cakework.com

  12. 12RN
  13. 13RU
  14. 14RC
  15. 15FF
  16. 16DR

    We’ve built SQLRooms, an open-source framework for creating single-node data analytics apps powered by DuckDB. It lets you build fully client-side, data-centric apps using React and DuckDB running in the browser (via WebAssembly) or in Electron. No server or backend is required — apps can work offline, preserve data privacy, and run queries on large datasets with sub-second performance. Features: - Query large datasets in browser with DuckDB (WASM) - Modular design for building composable data UIs (query editors, dashboards, notebooks, etc.) - Data privacy-preserving AI assistant that can…

    2025 · sqlrooms.org

  17. 17CH

    Hi, I'm fiiv, and I'm the creator of Cache Horse. I built it because I wanted an easy plug-n-play solution to caching and simplifying HTTP requests - in particular, on frontend. First, I was fetching data like daily weather, historic currency exchange numbers, air quality readings - and many of those APIs have quota limits. And second, since I was already caching them, I thought it would be useful to batch them together - so I built that feature in. I would love to hear your feedback and thoughts on the project. Thanks!

    2025 · cache.horse

  18. 18CA

    I’ve been experimenting with building a Node.js HTTP framework using Rust + Hyper with N-Api. The project started as a fully synchronous server, but I recently patched it to support async (Tokio/Hyper). That change alone nearly doubled throughput in benchmarks. What’s different: * Built directly on Hyper, no heavy abstraction * napi glue for Node.js bindings * Minimal core (sync and async engines side-by-side) * Focused on raw performance, not plugins (yet) This is still experimental and not production-ready. I’d like feedback on: * Async API design — does it feel ergonomic? *…

    2025

  19. 192R
  20. 20YA
  21. 21UH
  22. 22DN
  23. 23RA
  24. 24CH

Ranked by how close each launch is in meaning, then by votes. Refine with a description →