CODEWITHSUNDEEP
google-drive-api
Robson Faxas
Robson Faxas

Reputation: 33

Google Drive API - Service account storage limitation - Alternatives

I'm developing a web application that's going to start with 200gb of data to be storaged. Over the years, the same application possibly can reach 1tb, perhaps 2tb in 5 years.

What I want from this application is the clients to upload files to the server and the server then upload files do Google Drive, persisting the webviewlink on database. It's working this way on localhost.

I know two options for authentication for Google Drive API: client account and service account. Service Account's option fits better for me because I want the server to have control of the files, not the client have control. But Service Account can storage too few data and the storage limit can't be increased. The limit is something around 15gb I guess, not sure.

If the Service Account will not help me, what options would I have to storage 2tb of data or more? Should I find another way to storage the files?

I'd like to stay using Google. If there's not any option using Google Drive API, please, suggest anything else for this scenario.

Upvotes: 3

Views: 4652

Answers (1)

pinoyyid
pinoyyid

Reputation: 22296

You have a couple of options.

  1. Use a regular account instead of a Service Account. You will still need to pay for the storage, but it will work and you'll have everything in a single account. From your question "I want the server to have control of the files, not the client have control" I suspect you have looked at the OAuth quickstart examples and concluded that only end users can grant access. That's not the case. It's perfectly valid, and really quite simple, for your server app to grant access to an account it controls. See How do I authorise an app (web or installed) without user intervention? for how to do this.

  2. Use multiple Service Accounts and shard your data across them. The various accounts could all share their folders to a kinda master account which would then have a coherent view of the entire corpus.

Personally I'd go with option 1 because it's the easiest to set up and manage.

Either way, make sure you understand how Google will want to charge you for the storage. For example, although each Service Account has a free quota, it is ultimately owned by the regular user that created it and the standard user quota limits and charges probably apply to that user.

Upvotes: 2

Related Questions