[google-appengine] Re: Best practicies for making GAE microservices idempotent

Just a quick note: while GAE supports named tasks and transactional enqueuing of tasks, it does not support the transactional enqueing of named tasks. Just a small detail to be aware of when architecting your application. Attila -- You received this message because you are subscribed to the

[google-appengine] Re: gae php mail quota too low, error?

Google Groups discussion forum is meant for open-ended discussions. This issue is leading to an increasingly specific situation and may potentially qualify as a defect on the platform. As such, I would recommend you submit a public issue tracker which most

[google-appengine] Re: gae php mail quota too low, error?

Please Google check this problem out! It must be a bug in the quota limits! -- 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 email to

[google-appengine] Re: GAE Firewall - Allowing Access for PubSub Push Subscriptions?

Hello JP, The architecture for push subscriptions does not seem to require such a magic URL as the in case of UrlFetch, as there is no user-configurable firewall involved in the delivery path. "The Pub/Sub server sends any messages for your subscription to the webhook address you have

Re: [google-appengine] Re: Best practicies for making GAE microservices idempotent

Sorry, I don't have operational experience with Cloud Spanner. It didn't exist when Fantasm was written. On Monday, 9 October 2017 07:32:13 UTC-7, Nilson Pontello wrote: > > Thanks for the clarification, It looks like I will have to keep hitting > datastore for my use case. > > BTW: Can

Re: [google-appengine] Re: Best practicies for making GAE microservices idempotent

Thanks for the clarification, It looks like I will have to keep hitting datastore for my use case. BTW: Can Fantasm benefit from making lock transactions using cloud spanner instead of datastore? or is datastore faster for small transactions like the ones

Re: [google-appengine] Re: Best practicies for making GAE microservices idempotent

No. You can't make that assumption about task queue delivery, though it's very, very good. This is why Fantasm had to go the extra distance with Datastore transactions. BTW, Fantasm allows you to turn off the Datastore run-once check and rely solely on task queue because in practice, task queue

[google-appengine] Re: Best practicies for making GAE microservices idempotent

Thanks Jason/George, My code does a job very similar to lock.py (this is what I am trying to avoid). So it looks like the secret is around task queues. Can I assume that enqueued tasks will be delivered *just once *(if my

[google-appengine] Re: Help me mail

You could set up a relay proxy for SMTP running on a high port that connects to your customers SMTP server and connect to that. T On Friday, October 6, 2017 at 9:05:36 PM UTC+8, Karl Tinawi wrote: > > Hi George/all, > > We're a small startup and we've invested in Google Cloud infrastructure >