Local Reactor Service

[CallmeT-ty]

Local backend service with stripped down apollo interface that starts the reactor. Take switchboard and simplify it:

• Making use of the filesystem storage.
• Removes any dependencies on graphql playground, postgress, cloud infra, redis, etc..
• Support for (both the websocket) & http service
• All logic that is in graphql controllers should be moved to the reactor instead except for input mapping
• No specific doc; mods need to be supported only synchronisation and command mutations.
• Drive 'stuff': Drive functionality should be working. (Listing drives, create a new one, default drive functionality etc;)

Make all of the above installable as a package. powerhousedao/reactor-service which functions as a graphql wrapper around the reactor.

[CallmeT-ty]

@acaldas @CallmeT-ty add package names we wanted to use

[acaldas]

Projects can do npm install @powerhousedao/connect and npm run connect to run the app locally.

[acaldas]

// reactor service accepts document drive as argument and returns express server // it's a express app // wraps document-drive with Graphql API

// switchboard // 1 init cache and db // 2 create document drive server // 3 call ReactorService(server) which returns an express server; // 4 wraps reactor service api with auth api

// CLI service runner // init connect studio // 1 memory cache + filesystem db (pgqlite in the future) // 2 create document drive server // 3 call ReactorService(server); // 4 add listener + trigger for connect studio // 5 add internal listener to auto-generate document models

• Frank

  1. rebase with main (format and lint rules)
  2. move subgraph to reactor-service (express app)
  3. move drizzle to document-drive storage adapter
  4. improve internal listener support in document-drive

• acaldas

  1. init reactor-service package (init document drive) set up ts, bundler, dev, and document drive import.
  2. add listener + trigger for connect studio
  3. add internal listener to auto-generate document models

Backlog:

• add websocket listener
• use reactor-service in switchboard (re-use express app with auth middleware?)
• drizzle storage adapter
  • optimistic concurrency control (version field on sync unit table)
• export read model from document-model-libs