add initial goals documentation #1

Merged
patrik merged 8 commits from goals into main 2025-12-01 13:48:39 +01:00
Showing only changes of commit 06c73db057 - Show all commits

View file

@ -11,10 +11,10 @@
- **Data Directory:** Defines where cached media files are stored.
- **Optional Name:** Human-readable CDN identifier (used for UI labeling and dynamic DNS registration).
- **Mode:** Can operate as a **shared CDN** (available to multiple users) or a **local-only CDN**.
- What content does a CDN node deliver:
- media (for starter)
- **Secure Connectivity:**
- Each CDN connects to the **main metadata server** using a **pre-shared key** for authentication and trust establishment.
- This ensures only authorized CDNs can register and exchange data with the main network.
- **Secure Connectivity**
blint marked this conversation as resolved Outdated

This isn't a goal, that's an explanation.

This isn't a goal, that's an explanation.
- **Dynamic Registration & Discovery:**
marcsello marked this conversation as resolved Outdated

What are device limits exactly?

What are device limits exactly?

Just too much copying and pasting. It should not be there.

Just too much copying and pasting. It should not be there.

Removed

Removed
- Upon startup, the CDN connects to the **main metadata server** and automatically registers itself.
@ -28,12 +28,10 @@
1. **Request content replication:** Copy or prefetch the content from another CDN or the main server.
2. **Stream fallback:** Stream the content directly from the main server or the nearest available CDN.
- **Peer-to-Peer (P2P) Sharing:**
- CDNs and the main server interconnect via **P2P protocols** to simplify file transfer and reduce reliance on centralized infrastructure.
- This enables faster, bandwidth-efficient distribution of popular content between geographically distributed CDNs.
- **Peer-to-Peer (P2P) Sharing**
blint marked this conversation as resolved Outdated

I think this would be better in the "Nice to have/later" part. Sounds a bit complex to be a core feature. (especially if you want to pack all this up to a single binary)

I think this would be better in the "Nice to have/later" part. Sounds a bit complex to be a core feature. (especially if you want to pack all this up to a single binary)
- **Federation & Collaboration:**
blint marked this conversation as resolved

This is not a goal, this is an explanation.

This is not a goal, this is an explanation.
- Multiple CDNs can share content and metadata within a trusted federation network.
- Multiple CDNs can share content and metadata within a connection between the instances via a secure tunnel.
- The system can automatically balance or replicate popular content across CDNs to optimize bandwidth usage and ensure availability.
blint marked this conversation as resolved Outdated

What does a "trusted federation network" mean in this context?

What does a "trusted federation network" mean in this context?

a connection between the instances via VPN

a connection between the instances via VPN

I think we should write that instead. To me it's more exact and therefore easier to understand.

I think we should write that instead. To me it's more exact and therefore easier to understand.
- **Metadata Management:**