3 ms·

Side note: As someone who wanted a high level overview of Durable Objects, the Cloudflare announcement page 404s https://blog.cloudflare.com/introducing-worker

• kentonv 4y ago
  Thanks for catching this. Not sure what happened exactly but jiggling the handle (republishing the post) seems to have fixed it.
  • ianbutler 4y ago
    Yup, and thank you for fixing it!
• quickthrower2 4y ago
  This sounds magical: > Durable Objects make this easy. Not only do they make it easy to assign a coordination point, but Cloudflare will automatically create the coordinator close to the users using it and migrate it as needed, minimizing latency.
  • strix_varius 4y ago
    It sounds magical. I would recommend trying it first... the experience of trying to actually build anything with it is quite un-magical. The documentation, CLI, workflow, and pricing (for sockets especially) all fall quite short.
    • quickthrower2 4y ago
      I agree. I have learned as a general idea "use the fancy new thing if the pain of not using it is costing you a lot of money", because having your data nice and structured, typechecked in a relation DB with a query engine is the sweet spot for most applications. Firebase taught me this lesson. If you have an app with user ids and user profiles, and another records (plural) references them, you need a join, and non-relation databases suck at joining data. Having data flung about the place in these objects sounds a bit scary (how do I back them up, and keep track of them, how do I join data from multiple objects, and what if those different objects are all around the world).