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

saved by

• Jacky Zhao
• Amir
• Karan MJ
• CJ Quines
• Hamidah Oderinwale
• Devin Plumb
• Curius App
• Danish

related reading

• How's Linear so fast? A technical breakdownperformance.dev
• Build Your Own Databasenan.fyi
• The Elements of UI Engineering — overreactedoverreacted.io
• A Graph-Based Firebasestopa.io
• A More Human Approach To Databasesccorcos.github.io
• Build your own Reactpomb.us
• Materialized views are obviously useful – Sophie Alpertsophiebits.com
• Against SQLscattered-thoughts.net
• Pure UIrauchg.com
• Potluck: Dynamic documents as personal softwareinkandswitch.com
• How Does a Database Work?cstack.github.io
• Towards a unified theory of reactive UI | Raph Levien’s blographlinus.github.io