3 ms·
> Does this imply that another guest Worker can impact/takedown my Worker due to their tasks misbehaving? No, the system is designed to prevent that. Each gues
by kentonv 5y ago
> Does this imply that another guest Worker can impact/takedown my Worker due to their tasks misbehaving?
No, the system is designed to prevent that. Each guest runs in its own V8 isolate which we carefully control to prevent interference.
(Of course, all software has bugs from time to time. But we consider it a security flaw if one worker can somehow disrupt other workers, and handle it accordingly.)
- tiffanyh 5y agoAwesome. Thanks so much. Any considersation to expanding the Worker use case to allow for more deployment of full-blown web apps to the edge?
- kentonv 5y agoOf course! Many people are deploying full-blown web apps on Workers today. We're constantly working on new features to fill in gaps so more types of apps can be built entirely on Workers. Durable Objects, cron triggers, increasing the time limit from 50ms to 30 seconds (and eventually 15 minutes), etc. are all part of this, and we have more coming.
- tiffanyh 5y agoAny talk of a SQL database offering? The KV is awesome but there are times when a relational database is a way better fit. E.g. I'd love to be able to deploy a full blown Elixir/Phoenix/Postgres app to Cloudflare Workers.