You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is already possible outside of SQLite and many are doing it .
i guess the question is does kundalini want to enable it or do it ?
For example there are many projects use NATS leaf and nats Server to do the edge / cloud use case.
Also for wasm udf using NATS.
They all use a semi ES / CQRS architecture overlay but not all.
CQRS is the “Turning the Database inside out “ setup. So it’s highly related to lib sql.
The problem is as always focus, so I am wondering if there is interest in this area.
i read the vision and it makes a lot of sense .
What is missing ??
Tooling to manage schena where types are evolving over time. If the types are managed by a db then it’s easier. The thing is that those types exist higher up in middle tier and higher. If the db is the db and middle tier with wasm udf inside this problem becomes moot .
Reminds me of lotus notes and couch db relax. The db is everything.
It’s ok because you can have lots of those db with a decent replication strategy. So you can scale and have core dbs , regional dbs , cdn dbs and on-site edge dbs.
Often a mutation on edge needs to travel towards the core, the core does the transaction and the resulting data then ripples back towards the edge. This all works pretty well in a ES / CQRS setup.
Anyways … would be good to see what people think and to discuss.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is already possible outside of SQLite and many are doing it .
i guess the question is does kundalini want to enable it or do it ?
For example there are many projects use NATS leaf and nats Server to do the edge / cloud use case.
Also for wasm udf using NATS.
They all use a semi ES / CQRS architecture overlay but not all.
CQRS is the “Turning the Database inside out “ setup. So it’s highly related to lib sql.
The problem is as always focus, so I am wondering if there is interest in this area.
i read the vision and it makes a lot of sense .
What is missing ??
Tooling to manage schena where types are evolving over time. If the types are managed by a db then it’s easier. The thing is that those types exist higher up in middle tier and higher. If the db is the db and middle tier with wasm udf inside this problem becomes moot .
Reminds me of lotus notes and couch db relax. The db is everything.
It’s ok because you can have lots of those db with a decent replication strategy. So you can scale and have core dbs , regional dbs , cdn dbs and on-site edge dbs.
Often a mutation on edge needs to travel towards the core, the core does the transaction and the resulting data then ripples back towards the edge. This all works pretty well in a ES / CQRS setup.
Anyways … would be good to see what people think and to discuss.
Beta Was this translation helpful? Give feedback.
All reactions