Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Workers KV

blog.cloudflare.com

Post reply on HN
Print view View original

11–20 of 103 posts

Re: Introducing Workers KV

#11

Post by scoggs »

zackbloom wrote: post #7
chrisweekly wrote: post #6

This is really cool. Webapps are basically programs that are executed across the network; having fine-grained control over what happens at each layer (client, client service worker, edge nodes, proxy server, origin server) means more choices and complexity, but also so much more power.

The question I would ask is: once you have the ability to run code and store data on the network itself (which Cloudflare effectively is), why do you need an origin at all?

I could be understanding the crux of your question wrong but I believe the point the article and technology makes over and over is that it offloads nearly all of the stress and communication off of the backend and instead replaces it with a Worker KV which converts into becoming one static call and then everything is handled within the Worker. The applications seemed vast and only limited by creativity, as well.

Re: Introducing Workers KV

#13

Post by zackbloom »

webjames wrote: post #9

With the shopping cart example, I'm not sure I understand how session identity can be preserved if I clear my local storage/cookies?

It's moving that shopping cart data from being stored at a single origin, to being stored in the network all around the world. The advantage of that in that use-case is you can render your site just as quickly as if it was a static website, but it can contain the customer's personal shopping cart data.

Re: Introducing Workers KV

#14

Post by OJFord »

The feature aside, this is a really great blog post: learning a bit about the history of the feature, even if only tangentially related (Babbage and the Analytical Engine) in the intro is great.

Re: Introducing Workers KV

#15

Post by jgrahamc »

OJFord wrote: post #14

The feature aside, this is a really great blog post: learning a bit about the history of the feature, even if only tangentially related (Babbage and the Analytical Engine) in the intro is great.

Thank you; that's kind.

Re: Introducing Workers KV

#16

Post by tyingq »

zackbloom wrote: post #7
chrisweekly wrote: post #6

This is really cool. Webapps are basically programs that are executed across the network; having fine-grained control over what happens at each layer (client, client service worker, edge nodes, proxy server, origin server) means more choices and complexity, but also so much more power.

The question I would ask is: once you have the ability to run code and store data on the network itself (which Cloudflare effectively is), why do you need an origin at all?

One write per second, per key plus eventually consistent does limit the functionality a bit.

You're right for some use cases though.

Re: Introducing Workers KV

#17

Post by manigandham »

zackbloom wrote: post #7
chrisweekly wrote: post #6

This is really cool. Webapps are basically programs that are executed across the network; having fine-grained control over what happens at each layer (client, client service worker, edge nodes, proxy server, origin server) means more choices and complexity, but also so much more power.

The question I would ask is: once you have the ability to run code and store data on the network itself (which Cloudflare effectively is), why do you need an origin at all?

You work for Cloudflare so that's a fun question but realistically there are still plenty of limitations. The script size, number of routes, KV consistency, write limits, and simple get/put API, etc.

It can work for simple apps but there's a long way to go before any serious enterprise system will be hosted entirely on a FaaS system like Workers.

Re: Introducing Workers KV

#20

Post by adventured »

zackbloom wrote: post #7
chrisweekly wrote: post #6

This is really cool. Webapps are basically programs that are executed across the network; having fine-grained control over what happens at each layer (client, client service worker, edge nodes, proxy server, origin server) means more choices and complexity, but also so much more power.

The question I would ask is: once you have the ability to run code and store data on the network itself (which Cloudflare effectively is), why do you need an origin at all?

> why do you need an origin at all?

At the point that CF replaces the origin, it is the origin.

The confusion in your query is the idea that "origin" is a rigid, fixed concept rather than flexible.

Post reply on HN