https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • d
    even if the timezones of the user, the poll and whatever won't be the same, and you could be in an edge case where a submitted user date isn't in the same month as the storage date
  • c
    So Date.now() is different based on where each edge is located?
  • c
    So I should be storing:
    Copy code
    js
new Date().toISOString()
  • d
    Date.now()
    is fine, and so is 
    new Date()
    - JS uses UTC timestamps internally. What I'm trying to say is that if you are located in a different timezone, and it is the 1st day of a month, just after midnight, your 
    new Date()
    might still be in the last month
  • c
    So the most reliable way would be to loop thru keys and delete old ones.
  • c
    So basically I can do this every few weeks or months.
  • d
    depending on how many votes you're expecting, you can calculate the optimal alarm call vs storage amount cost
  • d
    I'd just leave the ones from the last day of the previous month in place, after 24 hours you should be safe to delete
  • c
    Thanks
  • c
    For votes probably maximum 200 000 per poll per month.
  • c
    and each vote will store date in milliseconds + IP
  • c
    so 2 keys per vote
  • c
    That's why it would be a lot easier to just delete everything at the end of the month, but it won't be reliable as they could vote again at that time.
  • c
    When someone vote I'm increasing votes and votes_total columns in D1.
  • c
    If DOs are faster, I can also move those to DOs.
  • c
    But I also don't store who voted. DO will just prevent the same username and the same IP to vote again in the same day.
  • c
    So I can also start logging usernames in DOs and how many votes they made per month.
  • s
    When using list, can I use the end and limit options to get the previous limit number of results? Or will it just return results from the start, but less then limit if it encounters the end key?
  • c
    The paragraph that HardAtWork linked you to links to https://blog.cloudflare.com/durable-objects-alarms/ which does have an example usage of alarms. For better or worse, a lot of cloudflare documentation, not just for DOs, links to blog posts for more detailed discussion / examples.
  • c
    Thanks
  • c
    Is:
    Copy code
    toml
compatibility_flags = ["durable_object_alarms"]
    still needed?
  • c
    no
  • c
    thanks
  • c
    That's why I usually don't like blogs as most things are outdated-
  • c
    docs seems to be up to date
  • d
    If you check the docs on compatibility dates, it mentions the earliest date after which alarms are enabled by default
  • c
    DO reads seems to be cheaper than KV reads, but I should probably still cache DO results to KV for faster access and to not put too much load on DO right?
  • z
    DO reads are priced differently, you pay per 4kb (iirc) segment instead of per object read.
  • h
    DO reads are definitely faster than KV reads
  • h
    Especially since a read can be in memory
1...528529530...567Latest