4 ms·

Cool tech - basically CGI for WASM. I can't think of a use case though, usually everything I do server-side requires some form of persistence. Any ideas?

• methyl 4y ago
  Cloudflare Workers have a few ways to persist data, check out KV and D1
  • kentonv 4y ago
    Don't forget Durable Objects, which is a more fundamental building block. https://blog.cloudflare.com/introducing-workers-durable-objects/ https://blog.cloudflare.com/introducing-workers-durable-obje...
• solardev 4y ago
  You can persist data with their edge stores (see the sibling comment), or use it to transpose between different API schemas, or as an API gateway that fetches consolidates, consolidates, and caches multiple micro-endpoints, or use it to run Doom (https://blog.cloudflare.com/doom-multiplayer-workers/ https://blog.cloudflare.com/doom-multiplayer-workers/) or IRC (https://github.com/cloudflare/workers-chat-demo https://github.com/cloudflare/workers-chat-demo) a variety of smaller useful things (https://developers.cloudflare.com/workers/examples/ https://developers.cloudflare.com/workers/examples/) I am not affiliated with Cloudflare, but Workers is by far my favorite cloud/serverless platform -- so much simpler and faster than Lambda, etc. (if your use case is simple enough)
• AtNightWeCode 4y ago
  You can persist data in the key-value data store, as durable objects or in the R2 buckets (S3 like storage). So that is not a problem. There are other issues with CF workers though.
• pjmlp 4y ago
  Yeah, I have a name for them, lets call them servlets.
  • agambrahma 4y ago
    Hah, I see what you did there