News for hackers. Stuff that matters.

A comment on Three Years on Google App Engine. Parent comment

Re:Three Years on Google App Engine by thesandlord on Sunday December 31, 2017 @04:10PM (#16043009)
> What Google should consider doing is making App Engine "classic" services like Memcached, etc. available to any service running across GCP.

Already being done. First was Datastore, now Cloud Tasks is in Alpha. Expect to see others (Cron, Cache, etc) come as well.

[ Parent | on HN ]
Re:Three Years on Google App Engine by karl42 on Sunday December 31, 2017 @06:27PM (#16043618)
But there is still no way to use ndb from outside App Engine standard, right?
[ Parent | on HN ]
Re:Three Years on Google App Engine by Jahava on Monday January 01, 2018 @09:05AM (#16046088)
> But there is still no way to use ndb from outside App Engine standard, right?

Shameless plug, but for Go, there is an unofficial third-party (Chromium team) datastore package that feature near-seamless AppEngine standard/flex datastore support: https://chromium.googlesource.com/infra/luci/gae/+/master

It currently couples to any hosted memcached service, but should be forward-compatible with AppEngine if/when they release a Flex-accessible cloud version of their hosted memcache.

"luci/gae" also features a fully-compliant in-memory datastore mock for 1000x+ faster datastore testing and uses a memcache implementation based on "qedus/nds" which fixes several consistency issues present in "ndb".

[ Parent | on HN ]