Reload chat and Decouple the update module #1382
Merged
Conversation
This file contains hidden or 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
Signed-off-by: A-Mavericks <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
benjamin-747
approved these changes
Aug 27, 2025
Merged
via the queue into
web3infra-foundation:main
with commit Aug 27, 2025
53aa486
7 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Design Considerations
Chat Module
The chat module will be implemented as a long-running service that continuously runs within the system. It will expose its functionality through port 30080, making it accessible for external clients and other internal services.
Upload Crate and Vector Database
To improve modularity and maintainability, the upload crate will be decoupled from the logic that updates the vector database. This separation ensures clearer module responsibilities and facilitates independent scaling or replacement of each component.
Deployment of the Upload Module(Implementation at deployment time)
In the Kubernetes environment, the upload module will not run as a persistent service. Instead, it will be deployed as a Kubernetes CronJob, ensuring that the upload process is executed at scheduled intervals. This design treats the upload module as a periodic batch task, aligning with the requirement for regular execution without keeping the service running continuously.