Skip to content

Memcache? #677

Description

@thomasbuchis

Is going to have support to appengine memcache soon?

Activity

  1. jgeewax commented on Jun 18, 2015

    @jgeewax
    Contributor

    For memcache, you should just use the memcache client library for Node JS. I think the bigger question is ... where do you point your memcache client ...? And I don't know the answer to that just yet.

    @ajessup Do you know where I'd point my Memcache client inside App Engine + Node ? Should I spin up my own machine running Memcache?

  2. added
    type: questionRequest for information or clarification. Not an issue.
    on Jun 18, 2015
  3. ajessup commented on Jun 21, 2015

    @ajessup

    The team is looking at adding native memcached support within the Managed VM, rather require than a proprietary API. Once that's available should be able to use a native node client library that can speak the memcached wire protocol (eg. https://www.npmjs.com/package/memcached) and point it to a particular port on localhost.

    When it's available we'll update the documentation at https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes with information like the port number you'll need to access it.

    In the meantime, spinning up a memcache cluster on GCE in the same zone as your Managed VM application seems like a great suggestion.

  4. jgeewax commented on Jun 21, 2015

    @jgeewax
    Contributor

    Cool -- going to close this out then. Thanks @ajessup

  5. loixlab commented on Feb 20, 2016

    @loixlab
    Contributor

    Just finding this thread now.
    @jgeewax Could you point me in the direction on how to setup the memcached library with GCE and my Managed VM?
    Thank you!

  6. jgeewax commented on Feb 21, 2016

    @jgeewax
    Contributor

    I think what @ajessup is saying would be to note where your VMs are in App Engine, and then turn on a GCE instance in that same cluster.

    Then you just point your memcache client at the GCE VM (make sure to open the ports for MC, should be 11211) so that you Managed VMs can talk to your Memcache VM.

    Does that make sense?

    If you're still having trouble, could you take this conversation over to StackOverflow ? Don't want this to get lost here in an GH issue :)

  7. ajessup commented on Feb 22, 2016

    @ajessup

    @sebelga Actually you can use App Engine's memcache service (which is available to every App Engine module, including those running Managed VMs). For Node.js, you can use any nodejs client library that supports the memcached wire protocol (which is why we haven't provided one in the gcloud library).

    You can read a more complete guide on working with Memcache here https://cloud.google.com/appengine/docs/managed-vms/nodejs/caching-application-data

  8. loixlab commented on Feb 22, 2016

    @loixlab
    Contributor

    Great, thank you @jgeewax and @ajessup for the info. I will have a look at the App Engine's memcache service.

  9. nalbion commented on Jun 28, 2017

    @nalbion

    Does this work from Cloud Functions?

  10. loixlab commented on Mar 13, 2018

    @loixlab
    Contributor

    For those who might be interested, I created a small library for caching entities.
    https://github.com/sebelga/gstore-cache
    It works with Redis and so should work from Cloud Functions

  11. benji commented on Nov 14, 2018

    @benji

    Is there anything at all to use the App Engine memcache service?
    I tried using https://github.com/googlearchive/appengine-nodejs but I am getting a connection timeout:
    Error: connect ETIMEDOUT 74.125.202.95:10001
    If the service is available I could use any nodejs memcache library but I don't know where to point it to. Is the service available at all?

  12. 14 remaining items

  13. added a commit that references this issue on Feb 2, 2026
  14. added a commit that references this issue on Feb 3, 2026
  15. added a commit that references this issue on Feb 3, 2026
  16. added a commit that references this issue on Feb 5, 2026
  17. added a commit that references this issue on Feb 23, 2026
  18. added a commit that references this issue on Feb 26, 2026
  19. added a commit that references this issue on Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions