msgbyte / msgbyte/tianji

Feature: Multi-Instance Integration with Unified View

Open
#133 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

I'd like to propose a new feature that enables multiple instances of Tianji to run simultaneously in different locations while consolidating data from all instances into a single main instance.

Objective:

  • Improve system availability and responsiveness by running multiple instances across various regions.
  • Provide a unified view of the system by integrating data from different instances, ensuring a seamless and comprehensive experience.

Perspectives:

  • Decentralized Architecture:
    Run separate instances in distinct locations with the ability to visually integrate their information, allowing for a more robust and fault-tolerant setup.
  • Hybrid Approach:
    Operate a single main instance alongside minimal agents deployed in other locations to collect uptime monitoring data, which is then periodically synced with the central instance.

Conclusion:

I would appreciate your thoughts on this proposed feature. I'm particularly interested in hearing from the code maintainers regarding the feasibility of implementing multi-instance integration and unified views.
Are there any technical challenges or concerns that need to be addressed?
What would be the estimated effort required to develop this feature?

Thank you.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by reviewing the project's architecture and existing data synchronization or monitoring boundaries to assess the decentralized and hybrid approaches. Done would require an agreed design for multi-instance data collection, synchronization, and a unified view.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.