Hello Yegor,
for my case the requests for large data are done from the client side,
the application only refers them. In that point an external storage,
objects with fixed URI are more feasible than passing data from
blobstorage consuming CPU cycles, blobstorage api calls. Thank you for
clearing it up.
btw: the google storage is provided in U.S. datacenters only, what
limits other developers to use the storage. But until it's an
"external" storage it's doesn't matter who provides the space.
Carpe diem
Perun
On 24. Mar., 15:51 h., Yegor <yegor.jba...@gmail.com> wrote:
> Hi, Ikai,
>
> Interactions between GAE apps and Blobstore are billed for storage +
> CPU. Google Storage is billed for storage + network + request count.
>
> How do the two compare in a real-world scenario from price/performance
> standpoint? It seems that Blobstore, being a core part of GAE, is
> regarded as "local" to your application, while Google Storage will be
> "external" and is therefore no different from Amazon S3 or Rackspace
> CloudFiles.
>
> There are also these URL Fetch 1mb-out/32mb-in limits, which seem to
> apply to everything. It's like we have a Titan 4 class rocket but
> we're only allowed to use a car engine to fly it.
>
> Cheers,
>
> Yegor
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
