Actor Store

[boorich]

This is a local actor store. Whatever is built and uploaded via the build tool will end up here with informative metadata. This way, we avoid using hashes, CIDs and addresses and may use human-readable names. We can include the following:

• Release/debug WASM bundle
• Code (possibility to create a template out of it)
• Labels and other metadata

As an extra, we could potentially point to remote Actor stores to have some additional templates available.

Technical scope Create Actor Store and commands to interact with it

• [ ] add
• [ ] remove
• [ ] template
• [ ] list
• [ ] modify

[LesnyRumcajs]

The idea behind this is that it's a persistent database behind a defined API. Any decent DB backend should do as we don't have any tight performance requirements, so whatever the folks implementing it are comfortable with.

Each record in the Actor table would consist of the binary blob bundle + metadata as defined within the build tool.

[morrigan]

The idea behind this is that it's a persistent database behind a defined API. Any decent DB backend should do as we don't have any tight performance requirements, so whatever the folks implementing it are comfortable with.

Each record in the Actor table would consist of the binary blob bundle + metadata as defined within the build tool.

@stonecharioteer want to propose a database type? :) might be good to lead something in a proposal and get feedback imemdiately

[stonecharioteer]

I've always been comfortable with PostgresQL. It can handle anything we can throw at it.