Depends what you're doing. Workers allow you more flexiblity overall, if you wanted to deny specific
Depends what you're doing. Workers allow you more flexiblity overall, if you wanted to deny specific paths, require auth, or have a directory listing, and then if you were using a worker for that, you'd have to use the Cache API if you wanted cache at all. If your goal is just to serve what's in your bucket, you can add a Cache rule on the bucket hostname to force caching and set a custom edge cache ttl or upload items with a cache-control header. You'd be avoiding the worker invocation costs as well, as it would still run even for cached items