-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update SPEAR architecture in /doc/design folder (#3)
- Loading branch information
Showing
2 changed files
with
30 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# SPEAR high-level design | ||
|
||
## Design principles | ||
SPEAR's first design principle is to help developers and end-users an easier approach to develop and deploy an AI Agent in Cloud-Edge integrated manner. | ||
|
||
### Scalable | ||
SPEAR aim to provide scalable agent service with the help of auto-scaling. | ||
|
||
### Performant | ||
SPEAR aim to serve Agent requests performant, with the help of prudently designed APIs and online scheduling system. | ||
|
||
## Workflow | ||
|
||
<div align="center"> | ||
<img width="500px" src="./img/spear-arch.png"></img> | ||
</div> | ||
|
||
### Offline Phase | ||
- Input: Code of existing agent framework (e.g., LangChain) | ||
- Output: Deployment instance and configuration | ||
- Key technology | ||
- Multi-instance selection | ||
- Automatic code generation | ||
|
||
### Online Phase | ||
- Input: Generated instance of offline phase | ||
- Output: Scalable and performant user request serving | ||
- Key technology | ||
- Cloud-edge-end integrated offloading | ||
- Agent-oriented auto-scaling |