Question: aiohttp vs. gRPC API

Open
#625 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
google-cloud, grpc, python
Domain
backend-api-design, cloud

Research direction

The issue mentions gcsfs, aiohttp, the GCS JSON API, and the Google Python client using gRPC, but names no files, tests, or entry points. First research the current request path and compare the relevant Google Cloud client APIs; the issue does not define an agreed change or a clear completion condition.

Written by the indexing model from the issue text.

Description

Hello! I was curious if there was a reason gcsfs uses aiohttp with the JSON API to query GCS rather than using the Google Python client which calls the gRPC API. AFAIK the gRPC API is a lot more efficient.

Dominant language
Python
Stars
398
Forks
181
Avg merge
2d 10h
Merged PRs (30d)
36

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fsspec/gcsfs

All issues in fsspec/gcsfs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.