-
Notifications
You must be signed in to change notification settings - Fork 2
Define architecture #3
Copy link
Copy link
Open
Description
Goal
Define how AppArray will work. While we expect to use a browser for regular usage there are plenty of open questions.
Questions
- agentless? we could alternatively inject a client (e.g. written in go) on a machine
- separate UI from definition?
- UI stack could use:
- TypeScript?
- React or Vue or Angular
- Elm
- Backend if needed could use:
- F#
- Elixir
- Ballerina?
- Node.js
- Next.js
- WebAssembly
- Deno.land
- Client/server communication could use:
- REST
- GraphQL
- GRPC
Must have
- Shell to interactivily add elements (aka whiteboard)
- Ability to open a shell (Unix ssh or Windows pwsh) on a remote machine
Nice to have
- Full IDE e.g. with Visual Studio Code plugin or Theia
- Open a SQL client
- Browse messages in queue with viewer
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels