11–20 of 47 posts
HOPL papers
Hopl II: https://dl.acm.org/doi/proceedings/10.1145/154766
Hopl III: https://dl.acm.org/doi/10.1145/1238844.1411838 (use next button on the left to proceed)
Lots of absolutely fascinating stuff in there.
Don't have any particular recommendations, but I do have a way of browsing that made me find a lot of interesting stuff. Go to https://dl.acm.org/conferences Click on the Conference with the subject area that interest you, like "Hypertext and Hypermedia" ( https://dl.acm.org/conference/ht ) Scroll down to "Most Popular" and sort by either Downloads or Cited. Go bananas with reading everything.
My pick is Jeff Dean's The Tail At Scale (2013) [1]. If you're interested in performance of web services, it's very, very well-written and describes a counterintuitive (but crucial!) phenomenon: your p99.99 latency can drive the entire user experience because of head-of-line blocking. As microservice architectures have gotten more popular, this has only become more important. It's a fiendishly difficult problem to ge…
Check out the ACM Tech Packs. They are curated lists of papers organized by topic. https://techpack.acm.org/
If you ever find an ACM (or IEEE) paper that you don't have access to, chances are you can find the preprint on one of the author's website. The easiest way is to search for the paper on Google Scholar and see if there is a link that says "[PDF]" or "All X versions".
And if that finally doesn't work out, there is always sci-hub.si and their alter egos (https://en.wikipedia.org/wiki/Sci-Hub)
Turing award lecture papers.
My immediate recommendations are the onward! papers, https://www.sigplan.org/Conferences/Onward/
My pick is Jeff Dean's The Tail At Scale (2013) [1]. If you're interested in performance of web services, it's very, very well-written and describes a counterintuitive (but crucial!) phenomenon: your p99.99 latency can drive the entire user experience because of head-of-line blocking. As microservice architectures have gotten more popular, this has only become more important. It's a fiendishly difficult problem to ge…
Could you elaborate on why this is any more crucial for microservices than it is monolith?
In reality maybe someone is able to make each microservice so much more performant and is able to deal with slow or failed requests gracefully in the UX. Some sites do, but it doesn't automatically by any means.
Check out the ACM Tech Packs. They are curated lists of papers organized by topic. https://techpack.acm.org/