Skip to content
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

Agents As A Service #637

Closed
prafulk9986 opened this issue Jan 8, 2025 · 4 comments
Closed

Agents As A Service #637

prafulk9986 opened this issue Jan 8, 2025 · 4 comments
Labels
question Further information is requested Stale

Comments

@prafulk9986
Copy link

Hi Team,
Thats me. https://www.linkedin.com/in/praful-kharche-586979198/.
I head the architecture for Digital Business Banking. I lead the IT strategy and architecture.
I have been following LlamaAgents and their approach which resonates the distributed enteprise application architecture.
'Agents as a Service' - Extremely unique perspective to look at and might feel the right way the enterprise distributed applications run in production for a good reason.
Can PydanticAI team start exploring on this bit, as we see distributed nature of Agents are the key to run the scalable enterprise applications in long run.
Please feel free to reach, happy to help if anything is needed.

https://www.linkedin.com/in/praful-kharche-586979198/

@samuelcolvin samuelcolvin added the question Further information is requested label Jan 8, 2025
@samuelcolvin
Copy link
Member

#528 will allow graphs to run on distributed systems.

Can you explain in more detail what exactly you need, and what challenges you're facing.

@izzyacademy
Copy link
Contributor

@prafulk9986 I just wanted to chime in briefly. I am seeing a growing trend where a lot of frameworks are trying to create complete solutions with very opiniated design choices but I think the Pydantic AI framework is aiming to be more of a tool or an ingredient you can use to build your own solution tailored in a way that suits your use cases. A lot of projects are getting bloated because they are trying to solve everybody's problems and this ends up pulling the maintainers in so many different directions. Based on what I am seeing so far, I think this one is going to be lean and opinionated structures like that might take a while before they happen. I am looking forward to hearing from you as to why you feel you need it to be in that format or approach.

Copy link

This issue is stale, and will be closed in 3 days if no reply is received.

@github-actions github-actions bot added the Stale label Jan 16, 2025
Copy link

Closing this issue as it has been inactive for 10 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

3 participants