https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • d
    if it compiles to es6 modules you construct and return a response instead
  • t
    Yes, I need to use 
    event.waitUntil()
    .
  • t
    But I don't see any of way accessing that class.
  • g
    It's not available with on the ESM stuff just yet. The team are working on adding it soon 🙂
  • d
    would a normal 
    await
    work?
  • t
    Thanks! How can I follow the development of that?
  • g
    Here, #802187271067140107 , and developer docs 🙂
  • a
    Hello, I was unable to signup for the beta on my account.
  • a
    When I click the Signup link it takes me to my dashboard 😦
  • g
    If you navigate to Workers, then durable objects, you should be able to enable the beta
  • a
    I couldn't find the link under my workers area. Ill try again ty
  • g
    should be in the top nav
  • a
    Curious if anyone can tell me, but would it be possible to store say a .wav in a durable object?
  • a
    I am trying to find limitations on them.
  • a
    I can't seem to find any data on size/data limitations.
  • g
    Memory is limited to 128MB, and each key-value is 32KB, (but unlimited key-values).
  • a
    So durable objects is essentially an in-memory object storage, like Memcached but distributed.
  • g
    A 
    .wav
    probably lends itself more to KV, since it's unlikely you need synchronized storage?
  • g
    KV has a max-size of 25MB per key
  • a
    Ah, KV sounds more ideal then.
  • b
    Data stored as JS fields are, of course, in-memory. But those stored via the actual storage API are durable: https://developers.cloudflare.com/workers/runtime-apis/durable-objects#transactional-storage-api
  • b
    But yes, KV would be a better fit for media files -- you could use it from a Durable Object
  • g
    I would think so! And people have been using KV for all sorts of stuff for ages, so probably more battle-tested for you 🙂
  • a
    @User And what are the limitations on on that?
  • b
    > Keys are limited to a max size of 2048 bytes and values are limited to 32 KiB
  • b
    That storage would typically be used for application data, and KV could hold media (like your .wav)
  • a
    @User Awesome, thank you. We're gonna put together a test.
  • a
    We need to serve .wavs to Twilio VERY quickly.
  • a
    And our current implementation was hosting a cluster of Memcached servers on AWS to be close to Twilio (AWS Hosted)
  • b
    If they don't change frequently you might try KV with the cacheTtl parameter https://developers.cloudflare.com/workers/runtime-apis/kv#cache-ttl
1...626364...567Latest