Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effector modules management #156

Open
mikevoronov opened this issue Apr 25, 2022 · 0 comments
Open

Effector modules management #156

mikevoronov opened this issue Apr 25, 2022 · 0 comments
Labels
A-modules area: everything relate to how a module is prcessed before in Marine C-feature category: a new feature request

Comments

@mikevoronov
Copy link
Member

Fluence service is a group of modules of three different types:

  • facade modules expose the API of an entire service that is callable from Aqua scripts
  • pure modules contain pure logic, and they can't access the filesystem or call external binaries
  • effector modules can access filesystem through WASI and call external binaries

The difference between pure and effector was made to allow node hosters to distinguish between (possibly harmful) effector and (harmless) pure modules. But at the moment in Marine there is no any difference between pure and effector types of modules.

@mikevoronov mikevoronov added C-feature category: a new feature request A-modules area: everything relate to how a module is prcessed before in Marine labels Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-modules area: everything relate to how a module is prcessed before in Marine C-feature category: a new feature request
Projects
None yet
Development

No branches or pull requests

1 participant