Update README.md
This commit is contained in:
26
README.md
26
README.md
@@ -1,30 +1,42 @@
|
|||||||
# Project Ideas
|
# Project Ideas
|
||||||
|
|
||||||
A curated list of challenging, systems-level project ideas I plan to build.
|
A curated list of challenging, project ideas I would like to build.
|
||||||
|
|
||||||
### 1. ORC Protocol Implementation
|
### 1. ORC Protocol Implementation
|
||||||
|
|
||||||
- **Status:** `Not Started`
|
- **Status:** `Not Started`
|
||||||
- **Concept:** A lightweight server and client for the [ORC Protocol](https://github.com/RickCarlino/orc-protocol/tree/main)
|
- **Concept:** A lightweight server and client for the [ORC
|
||||||
|
Protocol](https://github.com/RickCarlino/orc-protocol/tree/main)
|
||||||
|
|
||||||
### 2. Smart Cache API Gateway
|
### 2. Smart Cache API Gateway
|
||||||
|
|
||||||
- **Status:** `Not Started`
|
- **Status:** `Not Started`
|
||||||
- **Concept:** A standalone, intelligent caching layer. It would act as a gateway that uses a declarative configuration (e.g., YAML) to define complex caching and invalidation rules based on API routes, request headers, and data dependencies.
|
- **Concept:** A standalone, intelligent caching layer. It would act as a
|
||||||
|
gateway that uses a declarative configuration (e.g., YAML) to define complex
|
||||||
|
caching and invalidation rules based on API routes, request headers, and data
|
||||||
|
dependencies.
|
||||||
|
|
||||||
### 3. WASM based serverless platform
|
### 3. WASM based serverless platform
|
||||||
|
|
||||||
- **Status:** `Not Started`
|
- **Status:** `Not Started`
|
||||||
- **Concept:** A distributed, self-hosted serverless platform using WebAssembly for its core runtime.
|
- **Concept:** A distributed, self-hosted serverless platform using WebAssembly
|
||||||
|
for its core runtime.
|
||||||
- **Components:**
|
- **Components:**
|
||||||
- **Control Plane:** Manages function deployments and schedules invocations.
|
- **Control Plane:** Manages function deployments and schedules invocations.
|
||||||
- **Worker Nodes:** Execute functions in a secure, sandboxed WASM runtime.
|
- **Worker Nodes:** Execute functions in a secure, sandboxed WASM runtime.
|
||||||
- **CLI Tool:** For deploying and managing functions.
|
- **CLI Tool:** For deploying and managing functions.
|
||||||
- **Challenge:** Building a distributed system, leveraging WASM for fast/secure cold starts, and designing the custom protocols for node communication.
|
- **Challenge:** Building a distributed system, leveraging WASM for fast/secure
|
||||||
|
cold starts, and designing the custom protocols for node communication.
|
||||||
|
|
||||||
|
### 3.1 WASI runtime
|
||||||
|
|
||||||
|
- **Status:** `Not Started`
|
||||||
|
- **Concept:** A WASI runtime for WASM functions.
|
||||||
|
- **Challenge:** Parsing a WASM module, and executing it in a WASI runtime.
|
||||||
|
|
||||||
### 4. Animated fetch script
|
### 4. Animated fetch script
|
||||||
|
|
||||||
- **Status:** `Not Started`
|
- **Status:** `Not Started`
|
||||||
- **Concept:** A terminal fetch script that displays some sort of animation, be it just a random moving thing, or like a
|
- **Concept:** A terminal fetch script that displays some sort of animation, be
|
||||||
game of snake.
|
it just a random moving thing, or like a game of snake.
|
||||||
- **Challenge:** Creating complex interaction with a terminal.
|
- **Challenge:** Creating complex interaction with a terminal.
|
||||||
|
|||||||
Reference in New Issue
Block a user