[DRAFT] AAP-32854: Decouple Views from Pipelines #1498
Draft
+93
−9
Conversation
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
manstis
commented
Jan 17, 2025
| data = None | ||
| match event_type: | ||
| case "chat": | ||
| response = chat_service.send( |
There was a problem hiding this comment.
We'd send Cloud Events.. something I can refactor this PR to use... if there's any traction for it's full implementation.
manstis
commented
Jan 17, 2025
5267c49 to
af82656
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
=== DRAFT ===
=== DO NOT MERGE ===
Jira Issue: https://issues.redhat.com/browse/AAP-32854
Description
This PR demonstrates basic decoupling of our
View's from the LLM.This naive implementation simply uses synchronous Django Signals to emulate an Event Bus.
The thinking is that by decoupling
View's from LLM we could later deploy each pipeline as separate containers and have a real Event Broker, such asKNative, handle routing events to containers allowing us to improve scalability and fault tolerance.That said and done.. this could end up being an academic exercise as there needs to be a level of pragmatism between our needs and realising a idealised distributed system. Hence, this PR shows a basic implementation for a single endpoint: ChatBot.
Testing
N/A. PR to aid technical discussion.
Steps to test
N/A. PR to aid technical discussion.
Scenarios tested
N/A. PR to aid technical discussion.
Production deployment
=== DO NOT MERGE ===
=== DO NOT DEPLOY TO PRODUCTION ===
=== DO NOT PASS GO, DO NOT COLLECT $200 ===