PK you said a big truth, we used flexible environment very much, but now
environment.
Post by PKChannels are not exotic, we have been using them heavily and is a
headache for us to migrate.
This attitude of some GAE users to only care about the features they use
and call the other features exotic and in the cutting block is not helpful.
Keep in mind that what goes around comes around and the feature you depend
on will be next. If you do not use a feature that gets deprecated at least
stay silent and thankful. After all, for many GCP users with IaaS mentality
the whole GAE is exotic...
If this is how GCP does business maybe they should post a Dashboard of
each feature and how many customers use it so we know what to stay away
from..
--PK
PS btw I have been spending the thanksgiving holiday figuring out how to
migrate to a different log system and avoid/minimize the 30% price hike
coming on Dec 5. A lot of fun and good progress but I have customer
features to work on and would have preferred to be working on those
instead. I picked GAE so that I do not spend my resources doing platform
work and here I am day in/day out spending time rewriting and retesting
things that were working.
I agree, and I suspected you were talking about "Prospective Search", it
always seemed too specific, however, "Channels" were truly unique and
useful, if it was a scalable service, I would definitely use it - and I'm
saddened by it's passing (I use polling heavily on one project, and have a
nodejs/websocket system in another, if "Channels" bloomed, it would enrich
the experience significantly)
As my .02 for the original post, I somehow gave up on support long ago,
but it's not entirely bad either, as it is, appengine is very mature, and
even if it received 0 updates for years, it would still be useful - but -
indeed, receiving swift and practical technical support would've been great
https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY -
It's a bizarre one, when contention for one entity occurs, it's like the
transaction is proceeding with a corrupt ndb system, and causing an
exception that halts the execution, Instead of creating a public issue
tracker issue, I ended up re-structuring my architecture so contention is
less likely, it seemed like the easier option, I really didn't have the
energy to go through the issue tracker process
@Kaan Soral. Yes, we also heavily use the images service, it's invaluable
and we love it. We were also using mail, although it really wasn't a big
problem to move to an external service. (Though incoming is indeed more of
an issue) By exotic, I mean things like Prospective Search and
XMPP/Channels. I don't think too many people were really affected by those
deprecations.
It is what I meant, apologies if I was confusing
Where is the mail deprecation? Post a link if it's happening please. I
thought they were only no longer approving requests to expand beyond the
100 daily limit. Is that what you mean?
Hi
Thanks a lot for the reply again
For images, https://cloud.google.com/appengine/docs/python/images/ - the
1600 resize limit started to age a bit, I'm using the images service
heavily on https://geobird.com - and considering the recent 4K, 5K
resolutions, even bumping the limit to 2400 would improve dynamics a lot,
considering it would at least cover 1080p (Current solution is to just
serve images with "=s0" - considering most devices have retina resolutions
now, most images started becoming "=s0" - and a significant bandwidth is
wasted for clients)
If we analyse the case for the images service, it provides dynamic
resizing at instant availability, It's an invaluable service, I love
appengine because it provides building blocks like these - Instead of
depreciating such services, it would be lovely to see new ones, for
example, a "videos" service, even though I'm using Zencoder for video
processing, if we compare it to the ease of using the images service, it's
a heavy burden
@Mark Cummins, I don't know what service you are calling exotic and
less-used, It would be great if you could provide concrete examples,
interacting with other app engine users, you would be amazed how each
component is utilised and valued
If we analyse the case for mail, I personally was using it to send mails,
so, while the deprecation was an extreme nuisance, it wasn't the end of the
world, yet, communicating with others, I saw that some were using apps as
turnkey solutions, or, they were deploying singular apps for their clients,
so having a practical mail solution was crucial to them, some were handling
incoming email, while things were simple from the outgoing email
perspective, for an app that handled both incoming/outgoing email, the
deprecation was much more worrying
Heard loud and clear on action speaking louder than words. We have a lot
brewing and are excited to show it off when ready.
There have been some deprecation announcements lately. The objective here
is to bring App Engine in line with the rest of GCP. This is a challenging
effort because of how long App Engine pre-dates the rest of the system.
That being said, we do have our users best interests at heart and we
believe the future state will be a good one. Significant improvements have
been made to the App Engine Admin API, which officially went GA
<https://cloudplatform.googleblog.com/2016/08/automate-deployments-and-traffic-splitting-with-the-App-Engine-Admin-API.html>
a couple months ago.
Regarding mail, we are currently gathering requirements for a GCP wide
solution. For images, could you give more detail on exactly which limit
you're running up against and the scenario?
On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via
Hi Kaan,
On a side note, it is possible to receive regular emails from the Google
1. Access the Cloud Platform Console
2. Click the â3 vertical dotsâ on the top-right section of the menu
3. Navigate to preferences->Updates & Offers
4. Set email to âOnâ for Feature announcements
By doing this, you will receive emails about the latest feature
announcements on the Cloud Platform.
Cheers,
Alex
--
You received this message because you are subscribed to a topic in the
Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
<https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/10a025ef-815c-42a5-9540-b96f24de1090%40googlegroups.com
<https://groups.google.com/d/msgid/google-appengine/10a025ef-815c-42a5-9540-b96f24de1090%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/C9DD9A50-61B5-4DF9-9170-A50DE91464A9%40gae123.com
<https://groups.google.com/d/msgid/google-appengine/C9DD9A50-61B5-4DF9-9170-A50DE91464A9%40gae123.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.