Module, Package and Resource ID system to identify and track meta objects, safely extend system with installable packages

[VladymyrPylypchatin]

The system consists of modules. like node_modules.

System consists of the "Resources":

• Object types
• Object properties
• Action types
• Apps
• Pages
• Widgets
• Workflows
• etc.

Each resource is like a meta-object that defines a system object. E.g. Customer model is an object that defines customer. etc.

The resource can be only defined in "Modules"

Module can contain an unlimited number of resources (e.g. Apps, Objecgs, Pages, Workflows, etc)

Every module “EXTENDS” the system and registers Resources within a system.

Each module has a module.js or something similar that defines the contents of the module and resources it has.

Similar concepts are:

• Palantir projects
• Odoo modules

Module is basicly a location like in a palantir.

Each module can also have a package.json. Or something similar so you basically can publish a module as a package.

Packages are installed. A package is basically a module that contains multiple resources.

Also an important of this is future we plan our billing to be based on the resources changed. So we need to have a way to define and register each resource within a system

[VladymyrPylypchatin]

The goal of this system is to:

• Be able to package modules and distribute them through marketplace
• Be able safely install new modules that will extend the system
• Have a semantic alternative to the LOC changed metric to track changes in the system