2 ms·
Request for comments about queueing theory. This is a one-page GitHub README that introduces queueing theory and does it in context of software development, su
by jph 8y ago
Request for comments about queueing theory.
This is a one-page GitHub README that introduces queueing theory and does it in context of software development, such as product management, message queues, and devops.
I'm the author and glad to answer questions here or in the repo.
Examples from the page that are the most relevant to Hacker News readers are relevant for devops continuous delivery:
* Dτ = Delivery lead time. Some product teams know this as "from concept to customer" or "from spec complete to code complete".
* Dμ = Delivery service rate. Some devops teams know this as "continuous deployment frequency" or "shipping X times per day".
* Dε = Delivery error ratio. Some quality assurance teams call this "change fail rate" or "percentage of deployment rollbacks".
* Rτ = Restore lead time. Some site reliability engineers call this "time to restore service" or "mean time to restore (MTTR)".
- shay_ker 8y agoI think queuing theory can be applied to A LOT of different concepts in software development. For instance, some people at Netflix use it to do predictive load balancing: https://youtu.be/6NdxUY1La2I https://youtu.be/6NdxUY1La2I I, personally, have been very interested (something about instantaneous velocity?). Though I was always pretty bad at math, so it takes me a while to get a handle on things.