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.

Sign up for GitHub

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

Jump to bottom

Epic: Move from v8go to node #58

Open
FabianKramm opened this issue Jun 2, 2022 · 1 comment
Open

Epic: Move from v8go to node #58

FabianKramm opened this issue Jun 2, 2022 · 1 comment
Assignees
@lizardruss
Labels
kind/design needs architecture design

Comments

@FabianKramm
Copy link
Member

FabianKramm commented Jun 2, 2022 •
edited by loft-bot
Loading

Use Case

We want to move away from a direct v8 integration to a node based integration which has a couple of advantages:

  • Use all node packages inside jsPolicy
  • Use an event queue and allow async programming
  • Get an extensive api for network, file etc access

Implementation

Create multiple node processes which we communicate through IPC to start small webhook scripts
@anoop2811
Copy link

Would this also help to move and support ARM based instance types like Graviton in AWS?

@alexandradragodan alexandradragodan added kind/design needs architecture design and removed epic labels Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lizardruss lizardruss

Labels
kind/design needs architecture design
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lizardruss @anoop2811 @FabianKramm @loft-bot @alexandradragodan