Data API: Need and Design #1107
Replies: 3 comments 7 replies
-
RoAPI looks really cool🔗 https://github.com/roapi/roapi
Comments from @davidgasquezThis is probably the most straightforward way. Point RoAPI to your slowly changing dataset and have a bunch of API ready. Could be served via Cloud Run/Lambda to reduce costs. |
Beta Was this translation helpful? Give feedback.
-
SeaFowlWith Seafowl, datasets could be packaged and deployed on the edge (CF Workers, Fly.io, Serverless platform, ...). They've figured out things like caching and CDNs. They have a great end to end example showcasing some interesting features. |
Beta Was this translation helpful? Give feedback.
-
Spotted Radiant Earth's new Source Cooperative initiative.
Their demo is worth watching too! I think this is an awesome approach to distributing datasets. Paired with things like WASM DuckDB, you get beautiful and useful websites all served from static assets (the browser does the HTTP range requests in real time!). I've been applying the same ideas on a recent project and wanted to surface this approach (Parquet files on S3) as an easy step between no API/ CSV and REST/GraphQL API. |
Beta Was this translation helpful? Give feedback.
-
Main page: https://datahub.io/notes/design-data-api
Job Stories
My rough use case is: i want to push a dataset and get an API i can share with others for them to use.
Bonus: i can meter it and charge for it!
Tools to use
Beta Was this translation helpful? Give feedback.
All reactions