-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.Net: Adds Process Framework with Aspire demo #10614
.Net: Adds Process Framework with Aspire demo #10614
Conversation
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
…tic-kernel into demos/pf-with-aspire
@crickman FYI I had to disable warning CA2234 when calling the translatoragent and summaryagent APIs because we are using customer HttpClient with baseaddress built via .net service discovery. Passing URIs instead of string would bypass the base address thus making the http call fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rename the endpoints to /api/summarize and /api/translate. Looks like some indentation issues creeped in, including Tabs 😱
Motivation and Context
This demo aims to showcase how the Semantic Kernel Process Framework can be used with .NET Aspire. The Process Framework allows developers to create business processes based on events. Each step of the process can be an agent or native code.
Description
In this demo, I have defined the agents as external services, and each step will call these agents using HTTP requests. This setup allows .NET Aspire to add value by tracing the process using OpenTelemetry. Additionally, since each agent is a service, they can be restarted as needed using the .NET Aspire developer dashboard.
Why .NET Aspire?
Thanks to .NET Aspire, developers can leverage the developer dashboard to debug in real time the Process and all the agents running. Since the agents are single APIs, each can scale independently from each other.
Contribution Checklist