5 ms·
I posted that answer. If you have any additional questions or insights let me know.
by tlrobinson 16y ago
I posted that answer. If you have any additional questions or insights let me know.
- phlux 16y agoI thought it was terrific that you did this - I emailed the answer to myself so I can read it on the bus... It looked like you did a lot of research into it based on the sources you posted. How long did it take you to create that post? What is your primary area of interest -- If I post a question about some other infrastructure, would you give such a detailed response, or was this a one-off?
- tlrobinson 16y agoIt took maybe 4 hours, but it was fun and I learned a lot (not just about Heroku). I've been using Heroku since near the beginning (we were in YC W08 together) so I was already vaguely familiar with the architecture. It was mostly filling in the details. Infrastructure is a side interest that I'm trying to learn more about, so I can't guarantee I'll be able to answer your questions, but it's worth posting them anyway. Hopefully other people can answer as well (of course that's what I thought when I posted the Heroku question... I ended up answering it myself) Rather than directing the question at me, just post a normal question on Quora, and post the link here or message me.
- nodesocket 16y agoWell done sir.
- wccrawford 16y agoI've been wondering about the internals for a while, and only had a brief notion of what it was like. Thanks for doing all this research!
- uriel 16y agoMight be worth noting that Heroku has released Doozer as an open source project and link to its home at: https://github.com/ha/doozer https://github.com/ha/doozer
- tlrobinson 16y agoIt's already mentioned in the answer under "misc tech". I couldn't find a lot of info on how Doozer is actually used at Heroku though.
- fowlduck 16y agoThe routing mesh is less discriminating than you might think. There is no "global queue".