Building data-centric apps with a reactive relational database
We're exploring an approach to simplifying app development: storing all application and UI state in a client-side reactive relational database that provides a structured dataflow model.
Building data-centric apps with a reactive relational database Building apps is too hard. Even skilled programmers who don’t specialize in app development struggle to build simple interactive tools. We think that a lot of what makes app development hard is managing state : reacting and propagating changes as the user takes actions. We’re exploring a new way to manage data in apps by storing all app state—including the state of the UI—in a single reactive database . Instead of imperatively fetching data from the database, the user writes reactive queries that update with fresh results whenever
Explore this link on the map →saved by
related reading
- Everything I know about good system designseangoedecke.com
- A Graph-Based Firebasestopa.io
- Cleaned-up transcript of Rich Hickey's talk "Deconstructing the Database" · GitHubgist.github.com
- The Elements of UI Engineering — overreactedoverreacted.io
- Application State Management with Reactkentcdodds.com
- Towards a unified theory of reactive UI | Raph Levien’s blographlinus.github.io
- I'm All-In on Server-Side SQLite · The Fly Blogfly.io
- The Conductor Rewrite: What They Changed to Make It Fastperformance.dev
- You Might Not Need an Effect – Reactreact.dev
- What is Jazz?jazz.tools
- A More Human Approach To Databasesccorcos.github.io
- Remix: The Yang to React's Yinkentcdodds.com