Hacker News Reader

Comment by tracker1 | Hacker News Reader

This is very cool, but how do you limit an end user to only being able to read a given set of values. It seems to me that this scheme puts all credentials for access in the browser, and they'll be able to just run roughshod all over your data without constraints in place.

Can you create data spaces/keys for ones that are read-write per-user and others that are read-only for a given user?

View on HN

You write the Worker code which runs on our infrastructure, not in a browser. You have complete control over who can access which piece of data, as it's your code doing the accessing.

Thanks, I misunderstood that part... very cool indeed. What are the overhead limits for workers?

Aside, it seems like this could be really interesting combined to make an entire API with static delivery from S3 or Azure Blobs, with a backend on a cloud hosted database. With a lot of flexibility in between.

The ultimate goal is to let you do all of that within our network!

When you say overhead limit, are you talking about latency? Our goal is to keep reads on the order of 5ms in the 90th percentile.

I mean compute/memory for the workers... just a rough comparison of what that might look like. Will probably sign up for the early access and play around with it soon.

We limit you to 50ms of CPU and 128 MB of memory now, but we're working on ways of raising those limits.

Access to these values are programmed in your cloudflare worker script. It's up to you to decide how they can be accessed.

Reply on news.ycombinator.com