Skip to content

single-node #3

@petrubraha

Description

@petrubraha

This project won't receive any maintenance or updates (from me, other contributors are welcomed). However I will present a needed feature.

The server code was designed to be ran on a single machine. The service provided therefore has only one endpoint, and a single point of failure.

As described in the previous issue the system information is stored on RAM. Adding multiple server nodes would require information exchange between them. This issue aims to provide a plan (and implementation) for solving this problem.

Default approaches:

  • create a database
  • socket connection between these nodes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions