This repository was archived by the owner on Nov 10, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Architecture
Jessica Mulein edited this page Aug 13, 2021
·
7 revisions
- Work in Progress
For a given node:
(Blazor REST + GraphQL + OData)
[BrightChain API Node]
|| (internal communication)
||
\/ (whitener, basic file ingestion, retrieval, helpers, etc)
[BrightChain Service]
||
||
\/
(Connect to other nodes via custom TCP/UDP)
https://github.com/The-Revolution-Network/BrightChain/discussions/42
- EF Provider: EntityFramework provider that keeps a lightweight cache (if not running on a node, otherwise connects directly) of blocks for internal use only and pulls them from the API node as needed to provide data to the service
- BrightChain API Node / BrightChain Service are really the core and work together. Provides methods to ingest and retrieve data and connects to physical storage.
This is a work in progress/concept.
TOC | Intro | 1 - Arch | 2 - Auth | 3 - Quorum | 4 - Identity/Reputation | 5 - Contracts/Crypto
Documentation updated regularly. You can pull the revision history if you check out the wiki's git repo.
Please consider joining. Doesn't matter if you're new to coding or crypto. I/We can help! Devel & Collab