[Feat]: Need of persistent task store

[aryaraj132]

Is your feature request related to a problem? Please describe.

While developing a POC, I came to face the problem that we lack any persistent database support for the task store.

I ended up creating a Postgres wrapper of the task store.

The question is mainly do we add these implementation of TaskStore with persistent database support in this library it self, or there is no plan for such and this will remain the bare bone library.

I don't see the point of needing to write your own implementation or installing another library just for this.

Describe the solution you'd like

We can create implementation of TaskStore with different databases and release them as the part of library itself.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ajaynagotha]

@aryaraj132 you can develop an extension for one. Say a2a/postgress-store. We can't overload this library with all those implementation as a core feature

[benclarkeio]

A persistent task store is essential for production. It's important to keep the barrier to entry as low as possible. The Python package has a number of persistent task stores included.

[ajaynagotha]

A persistent task store is essential for production. It's important to keep the barrier to entry as low as possible. The Python package has a number of persistent task stores included.

Alright in that case I will try to re visit everything and I will try my best to come up with some solution

[aryaraj132]

@ajaynagotha I have already created a persistent store for Postgres, I can raise PR for the same and then extend over it

[ajaynagotha]

@ajaynagotha I have already created a persistent store for Postgres, I can raise PR for the same and then extend over it

I am glad to know that. You should definitely raise the pr once you are confident about it. I would love to contribute to it if anything is there

[DracoBlue]

In a2a-python it's implemented as additional packages (see https://github.com/a2aproject/a2a-python?tab=readme-ov-file#-installation for reference).

e.g.:

uv add "a2a-sdk[postgresql]"

And since we already have the entrypoint @a2a-js/sdk/server/express we could make one like @a2a-js/sdk/server/postgres for the nodejs/typescript world :)

[drew-foxall]

I've begun to take a look at this in support of my work around edge compatibility for a2a-js

Will try using these adapters in some of my a2a examples publishing them individually.
So long as everything works out I'll look to PR them back ^-^

https://github.com/drew-foxall/a2a-js-taskstore-adapters

[benclarkeio]

@drew-foxall I created a working pull request I'm using in production with support for SQLite, PostgreSQL, and MySQL with Drizzle 4 days ago. It would be great if you could review that pull request.

[aryaraj132]

@benclarkegithub I not entirely sure of the policy of the project about using third party dependencies, but I think ORMs should be mostly avoided in this case, my point being, the difference between in memory store and db persisted store should not be anything more than configuring the DB.

[aryaraj132]

@drew-foxall Your repository is private 😞 would love to have a look.

[aryaraj132]

I have also made progress in this area, I have relased the pg adapter of the task store in production at my company and its supporting our entire a2a workflow for around 2 months now, so I feel confident about releasing it.

I also came by the need to list all of my a2a tasks a feature which is not part of the in memory task store, so my pg adapter also extends that features, but whether to add it in task store or just leave it to users to extend is debatable

[benclarkeio]

@benclarkegithub I not entirely sure of the policy of the project about using third party dependencies, but I think ORMs should be mostly avoided in this case, my point being, the difference between in memory store and db persisted store should not be anything more than configuring the DB.

They are optional dependencies, the Python package uses SQLAlchemy for their DatabaseTaskStore which is equivalent. Without an ORM there would need to be a different class and instructions for each database. I've included some examples below.

• Python DatabaseTaskStore: https://github.com/a2aproject/a2a-python/blob/main/src/a2a/server/tasks/database_task_store.py
• Proposed JavaScript DatabaseTaskStore: https://github.com/a2aproject/a2a-js/pull/213/files#diff-653e8a511eaf9a3a84d4362015bdd217c5649b98265605de12e2f25b630b3d9f
• Proposed JavaScript README.md (unified instructions): https://github.com/a2aproject/a2a-js/pull/213/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

[drew-foxall]

@drew-foxall Your repository is private 😞 would love to have a look.

Apologies I've opened that up. I'm going to go ahead and test from here is the intention.