StackGuardian / StackGuardian/tirith
Tirith Client-Server architecture
Open
Nobody has claimed this yet.
brainstorm
need-discussion
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
We can implement client-server architecture in the provider-core architecture or even Tirith as a service. There are some cases for this, e.g. decoupling even more between Tirith provider and core, and also user don't need to install Tirith in their local, etc. Need to brainstorm more
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the provider-core architecture and the Tirith-as-a-service idea described in the issue. Document the client-server use cases, including decoupling the provider from core and avoiding local installation. Done means the proposed architecture and scope are agreed after the needed brainstorming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100