AToMPM / AToMPM/atompm

Launch python transformation engine as subprocess of nodejs?

Open
#145 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
25
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Hi,

I see that the "launch" script starts both a nodejs process and a python process in parallel. From what I understand, the nodejs process, which is the "main" process, needs the python process, but not the other way around, so wouldn't it be better to launch the python process as a child process from nodejs? In this way, the AToMPM backend can be understood as a single nodejs process, and killing it will also kill the python process. It will also make it unnecessary to have a complex launch script.

Best regards,
Joeri

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the launch script and tracing how the Node.js backend and Python transformation process are started and stopped. Check the process-lifecycle behavior described in the issue, then define completion as the backend being launched as one Node.js process with the Python process lifecycle handled consistently when it exits.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.