Switch to generated AlloyDBAdminAsyncClient over aiohttp.ClientSession

[jackwotherspoon]

AlloyDB has a generated package with support for an async client. Should look at switching to use it over the aiohttp.ClientSession that is currently being used to hit the admin API endpoints. Will want to investigate performance a bit before committing to this switch in case it degrades the performance.

AlloyDB Client package: https://pypi.org/project/google-cloud-alloydb/

Generated client: https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-alloydb/google/cloud/

[RahulDubey391]

Hi @enocom @jackwotherspoon , if this feature development is on halt, can I start working it? Or let me know if other is on priority which I can take

[jackwotherspoon]

@RahulDubey391 Thanks for the interest here 😄

I will let @enocom make the decision as he is now the owner of this library.

My two cents atleast is that it doesn't hurt to get a working draft PR that uses the AlloyDBAdminAsyncClient over the current aiohttp client. This will let us then run some tests to see if there is any performance differences between the different clients. The one thing to keep in mind @RahulDubey391 is that if the generated client performs worse we may not end up merging the PR, just something to be aware of before you commit time.

@enocom The nice side of switching over to the generated client is that you will get some free benefits like universe_domain support etc which I think is in the future work of this library anyway. (code ref)

[jackwotherspoon]

@RahulDubey391 Another good potential task would be #245 for async token refresh, it is a bit more straightforward in my eyes

[RahulDubey391]

Okay @jackwotherspoon , I'll do the analysis and get back to you. Will raise a PR with the remarks.