Google has just announced that it is deprecating cloud storage and effectively a major part of App Engine that
we are relying on. To make matters worse the window of time to its removal is quite short so we don’t have enough
time to rewrite and adapt all the various API’s and tools that rely on this API.
We have already started the process of migrating off App Engine completely both due to rising costs and Googles
horrible service/support. This will also allow us to finally support many long standing user requests such as more powerful
push API’s etc. since we will no longer be held back by App Engines limitations.
In fact our choice to leave App Engine completely was sealed last month as our App Engine expenses skyrocketed…
The App Engine console simply stated a cryptic “datastore reads” number that was very high/expensive. We normally cache
everything in memcache but still it seems that the number was really high. Unfortunately, this was the only number we had!
Google doesn’t provide any way of knowing which of our queries was responsible for the large number and to this day we have
no idea what is the actual trigger for this. When we opened a service call they decided that this was a “justified” charge without
providing us with any itemized listing detailing what we are charged for.
Due to all of that we decided to start a migration process even before the last announcement, this means a lot
will change in the backend for Codename One but most of these changes will be seamless and will be made in
pieces that won’t be noticeable. However we have 2 big features that would be very hard to migrate off App Engine:
We already worked with the big users of these API’s to help them migrate away as we started planning.
However, we might have missed some smaller users. If you rely on one of these API’s and
haven’t been in contact with us please let us know ASAP.
Notice that as we migrate some services might require that you build a new version of the app, e.g. sending
a log from the device (part of crash protection feature) would migrate seamlessly (and probably improve)
however, you would need to upgrade your users to a new version of the app in order to keep using the feature…
We will also need you to update URL’s for services such as push notification etc. as new URL’s become available.