Databases
StackOverflow2013
Postsdbo
POGoogle App Engine - prohibitively slow and expensive backup and restore?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle App Engine - prohibitively slow and expensive backup and restore?
    primarykey
    data
    text
    <p>After working on several GAE apps, some of which are being used for production, I have come to the conclusion that on this platform, backing up your production data is slow enough and expensive enough for us to transition to some other cloud based technology stack. </p> <p>In one of our production apps, we have around a million entities with an average size per entity of 1KB. So the total size of the data is around a GB which should not be a big deal, right? Here is the output of the bulkloader tool after fetching the entities from the app engine with default options:</p> <blockquote> <p>[INFO ] 948212 entities (608342497 bytes) transferred in 47722.7 seconds</p> </blockquote> <p>That is almost 13 hours. So if we wanted to set up an hourly backup system for our production data, that would be way beyond impossible with the current GAE toolset.</p> <p>The cost is another story. I tried using the datastore admin to copy entities to a different app which i thought we could use for backup. I first set the budget to $2 per day which quickly ran out at around 5000 entities, then i increased the budget to $10 per day which ran out again without being anywhere close to replicating the million entities. </p> <p>I obviously dont intend to spend $100 every time i need to back my 1 GB data up neither do i want to wait for hours (or even days) just so that my data would be backed up. So either I dont know something or Google App Engine is currently just an impractical way to write scalable production quality apps of meaningful size that can be easily backed up and restored.</p> <p>Is there a fast and cost-effective way to backup your data from a GAE app?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USYasser
    1. USYasser
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGoogle App Engine - prohibitively slow and expensive backup and restore?
      1. USBen Parsons
      1. VTFavorite
    2. VO
      singulars
      1. POGoogle App Engine - prohibitively slow and expensive backup and restore?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGoogle App Engine - prohibitively slow and expensive backup and restore?
      1. USCuong Thai
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload