[–] OliverM 4y ago ↗ Throw away your API servers, use a db in your frontend and your backend, and let the pair of them worry about syncing state.
[–] OliverM 4y ago ↗ Interesting & available libraries implementing parts of this particular vision (mentioned in the talk):- Google's Firebase (meh, though maybe Supabase is mature enough by now to replace this suggestion?)- Tinybase: https://tinybase.org- sql.js (SQLite compiled to js): https://sql.js.org/But there's no single stack available (yet). I'm suprised Nikita didn't mention datascript here (https://github.com/tonsky/datascript) given the neat compatibility it offers with other datalog databases, but maybe he feels it's too niche/immature?
[–] oxff 4y ago ↗ I guess the question to ask is why are there even "backends". [–] OliverM 4y ago ↗ They don't need to be traditional 'backend' services. Any mechanism of synchronising state between clients could be enough?
[–] OliverM 4y ago ↗ They don't need to be traditional 'backend' services. Any mechanism of synchronising state between clients could be enough?
4 comments
[ 3.1 ms ] story [ 14.3 ms ] thread- Google's Firebase (meh, though maybe Supabase is mature enough by now to replace this suggestion?)
- Tinybase: https://tinybase.org
- sql.js (SQLite compiled to js): https://sql.js.org/
But there's no single stack available (yet). I'm suprised Nikita didn't mention datascript here (https://github.com/tonsky/datascript) given the neat compatibility it offers with other datalog databases, but maybe he feels it's too niche/immature?