sql.js
rtk-query
sql.js | rtk-query | |
---|---|---|
43 | 47 | |
12,234 | 579 | |
0.6% | - | |
6.5 | 8.7 | |
11 days ago | almost 3 years ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sql.js
-
Show HN: Appendable – Index JSONL data and query via CDN
Hi HN! A friend and I were inspired by projects like https://github.com/sql-js/sql.js and the idea of querying files served over CDN with HTTP range requests. We started thinking: what would a database that was specifically designed for this type of use case look like? So we started building one, and we landed on a functional prototype that we're pretty proud of!
With our prototype, Appendable, we're able to serve and query large (GB+) datasets by hosting them on a static file host like Amazon S3 or Cloudflare R2 without running a separate server and worrying about things like tail latency, replication, and connection pooling -- all that is handled for us by the file hoster.
Additionally, one tenet that we have been following is Appendable won't touch your underlying data, so your jsonl file is preserved and we point at that data instead of consuming it into an Appendable-specific file format. This keeps your data yours and makes it easy to introspect the data: just open it up with your favorite editor aka vim.
We're curious what you think, we're excited to build this out further to get the performance even better and add features like pubsub. Everything is open source at https://github.com/kevmo314/appendable.
Kevin and Matthew
- How to show CRUD projects on Github?
-
I made a website where you can use SQLite in your browser
My project is powered by sql.js, I recommend checking that out if you're interested - https://github.com/sql-js/sql.js/
-
How to build interactive way to learn SQL using Next.js and database?
Maybe you can try to use some SQL database compiled as Web Assembly Modules? Like this one for example: https://github.com/sql-js/sql.js
-
Recommendations for data structure and storage
If you want to have persistence, then I would go with a database like Dexie, as it uses IndexedDB and has transactions. If you just want something that's in memory, you could look at Sql.js or something simple like lowdb.
-
I have a large JSON object (~2GB), what's the best way to make a site that lets you search through it and display the results without crashing?
not necessarily. you can host an html/js/sqlite site on github pages for free. json -> sqlite3 js -> sql
-
new release of : https://sql.js.org/
Link: https://sql.js.org
- Web-Projekt - Hilfe, weil ich nicht weiß, was ich benötige :S
- Learn Postgres at the Playground
-
Show HN: CSVFiddle – Query CSV files with DuckDB in the browser
Does it work with really large files? Like, >100mb or so. I was considering making something similar but with sqlite.js [1], but the problem with it is that it loads everything in memory, so I wasn't entirely sure how it will deal with larger workloads.
[1]: https://sql.js.org/#/
rtk-query
-
What I Learned as a Web Dev on My First React Native Project
The Redux library is quite a common choice thanks to its broad ecosystem. Luckily, there is now a very useful Redux Toolkit that mitigates the amount of boilerplate you have to usually write. RTK Query is a very new Redux solution for data fetching and caching, hopefully making our lives even easier. Though the web seems to slowly be moving away from Redux to React Query, SWR or other solutions, mobile is a different story; Redux is holding on to its popularity, as it integrates well with libraries that persist and rehydrate the global state for users when they relaunch the app.
-
Is there an effective solution for implementing data-fetching logic while keeping the codebase DRY?
rtk query is built-in to the redux toolkit starting from v 1.6
-
Using Redux vs Regular States?
For api data. Check out rtk query https://rtk-query-docs.netlify.app/ It is supposed to better for api data with redux. I have not yet tried it.
-
Kea: Production Ready React State Management
I haven't looked at Kea in a while, but I'll toss out some comparisons based on my knowledge of RTK and what I remember about Kea + looking at its docs.
Kea's main selling point is that it lets you define self-contained chunks of Redux logic. Initially, this is similar to RTK's `createSlice`, in that you're writing a set of "case reducers" + action creators. However, it also build in Redux-Saga as a general-purpose side effects approach, and lets you write "listeners" that respond to dispatched actions.
Where it particularly differs from RTK is in the amount of abstraction included. RTK tries to stay "visibly Redux" [0], and the abstractions are fairly thin - the focus is on simplifying the typical Redux code patterns, without hiding the fact that you're using Redux. Kea is much more heavily abstracted. It does use a number of Redux terms ("actions", "reducers", etc), but the code that you write looks noticeably different than a "typical" Redux app. Also, RTK focuses on thunks as the default async approach, rather than sagas [1]
I believe Kea also has some mechanisms for combining together those "logic" chunks in various ways, including doing so dynamically at runtime, and it appears to have some "lifecycle"-type callbacks for handling when those chunks get mounted and unmounted.
RTK Query [2] [3], on the other hand, is a purpose-built data-fetching abstraction, most similar to React Query and Apollo. Its only purpose is to fetch data from whatever URL endpoints you've defined, handle the loading state, update the cache with the results, and re-render whatever components care about that data.
I haven't actually used Kea myself, but it does appear to have some meaningful thought and development put into it. I would still recommend RTK as the default approach for anyone wanting to use Redux (and of course I'm biased there), but Kea has some interesting approaches.
[0] https://blog.isquaredsoftware.com/2019/10/redux-starter-kit-...
[1] https://blog.isquaredsoftware.com/2020/02/blogged-answers-wh...
[2] https://rtk-query-docs.netlify.app
[3] https://github.com/reduxjs/redux-toolkit/releases/tag/v1.6.0...
-
Redux Toolkit v1.6 alpha.1: RTK Query APIs integrated and smaller bundles with Redux 4.1!
https://github.com/rtk-incubator/rtk-query/issues/215#issuecomment-826344927
-
Apollo or redux for state?
tl;dr Apollo, URQL, SWR, react-query, nor even RTK Query are meant to be wholesale replacements for Redux which is meant for global state.
- RTK Query 0.3 Final Beta: custom query functions, lazy queries, and more!
-
Use case for redux-thunk?
You may want to look into our upcoming "RTK Query" API, which is specifically designed to abstract the process of fetching and caching data for Redux. We've got one more alpha release coming up that we're finalizing now, and then we'll be merging the APIs back into Redux Toolkit itself and releasing it.
-
Cousins playing nicely: Experimenting with NgRx Store and RTK Query
Redux provides state management that has been widely used across many different web ecosystems for a long time. NgRx provides a more opinionated, batteries-included framework for managing state and side effects in the Angular ecosystem based on the Redux pattern. Redux Toolkit provides users of Redux the same batteries-included approach with conveniences for setting up state management and side effects. The Redux Toolkit (RTK) team has recently released RTK Query, described as "an advanced data fetching and caching tool, designed to simplify common cases for loading data in a web application", built on top of Redux Toolkit and Redux internally. When I first read the documentation for RTK Query, it immediately piqued my interest in a few ways:
-
Need help in choosing state management library.
Check out RTK Query since you are already using Redux.
What are some alternatives?
localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.
redux-saga - An alternative side effect model for Redux apps
LokiJS - javascript embeddable / in-memory database
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
PouchDB - :koala: - PouchDB is a pocket-sized database.
zustand - 🐻 Bear necessities for state management in React
WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
DB.js - db.js is a wrapper for IndexedDB to make it easier to work against
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
litestream - Streaming replication for SQLite.
redux-persist - persist and rehydrate a redux store