search

rohan843 / dnncase

GNU General Public License v3.0
1 stars 0 forks source link

System Design Possibility #33

Open rohan843 opened 1 year ago

rohan843 commented 1 year ago

We can structure our system this way:

  1. Any running process/thread that does a single logical piece of work will be called a task.
  2. Each task can have access to MessageQueues that can be implemented via OS level pipes or some other slightly higher level IPC mechanism. (We can't use electron's in-built queues as certain tasks, such as model training, will be running from python files.)
  3. The system-side tasks, such as a visualizer can have access to these MessageQueues as well, and then can show real-time plots, or otherwise perform some computation.
  4. We can setup read streams from files as such task-MQ pair as well.
rohan843 commented 1 year ago

Can consider ZeroMQ or Redis for message queues.