browserify / browserify/wzrd.in
refactor to have separable build servers
- Dominant language
- JavaScript
- Stars
- 637
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
I think the end architecture should look something like,
```
--->(Actual Real CDN)--->(app-level cache/lookup)--->(gearman server)--->(builder workers)
```
The CDN can only cache specific routes. The app-level cache/lookup is still required for a number of reasons. Ideally, these would use a redis and there would be an extra worker for cache busting. Using gearman to separate off the builders nets an added bonus of being able to use docker or similar to sandbox.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides an architecture sketch but names no files, tests, or entry points. Begin by mapping the current build and cache flow, then compare it with the proposed CDN, app-level lookup, Gearman server, Redis cache, and separated builder workers. Done would require an agreed implementation scope and a working architecture that supports independent builders and cache busting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, redis
- Domain
- backend, build-system, distributed-systems, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100