r4um

41 ms·

1. 511.▲
   Compressive Strength and Parameter Passing in the Physics of Software [pdf](physicsofsoftware.com)

   2 points by r4um 11y ago|0 comments
2. 512.▲
   Docker containerd integration(blog.docker.com)

   1 points by r4um 11y ago|0 comments
3. 513.▲
   Consensus in the Cloud: Paxos Systems Demystified(muratbuffalo.blogspot.com)

   1 points by r4um 11y ago|0 comments
4. 514.▲
   Containers In Production: Case Studies, Part 1(thenewstack.io)

   3 points by r4um 11y ago|0 comments
5. 515.▲
   Unwinding Uber’s Most Efficient Service(medium.com)

   2 points by r4um 11y ago|0 comments
6. 516.▲
   Resilient ad serving at Twitter-scale(blog.twitter.com)

   1 points by r4um 11y ago|0 comments
7. 517.▲
   Immutability is not enough(codewords.recurse.com)

   271 points by r4um 11y ago|123 comments
8. 518.▲
   Beyond Round Robin: Load Balancing for Latency(blog.buoyant.io)

   2 points by r4um 11y ago|0 comments
9. 519.▲
   Efficient Queue Management for Cluster Scheduling [pdf](research.microsoft.com)

   3 points by r4um 11y ago|0 comments
10. 520.▲
    Best CPUs: Q1 2016(anandtech.com)

    3 points by r4um 11y ago|0 comments
11. 521.▲
    Measuring and Understanding Consistency at Facebook(muratbuffalo.blogspot.com)

    1 points by r4um 11y ago|0 comments
12. 522.▲
    Cliffhanger: Scaling Performance Cliffs in Web Memory Caches(blog.acolyer.org)

    1 points by r4um 11y ago|0 comments
13. 523.▲
    GC 'Nepotism' and Linked Queues(psy-lob-saw.blogspot.com)

    4 points by r4um 11y ago|0 comments
14. 524.▲
    Efficiency Over Speed: Getting More Performance Out of Kafka Consumer(signalfx.com)

    1 points by r4um 11y ago|0 comments
15. 525.▲
    Strong consistency in Manhattan(blog.twitter.com)

    1 points by r4um 11y ago|0 comments
16. 526.▲
    Elements of API design: Delivering a flawless NFL experience(yahooeng.tumblr.com)

    1 points by r4um 11y ago|0 comments
17. 527.▲
    Observability at Twitter: technical overview, part I(blog.twitter.com)

    1 points by r4um 11y ago|0 comments
18. 528.▲
    Is Your Computer Stable?(blog.codinghorror.com)

    2 points by r4um 11y ago|0 comments
19. 529.▲
    Clojure Work(clojurework.com)

    2 points by r4um 11y ago|0 comments
20. 530.▲
    Best practices for a new Go developer(blog.rubylearning.com)

    2 points by r4um 11y ago|0 comments
21. 531.▲
    How Complex Systems Fail(blog.acolyer.org)

    3 points by r4um 11y ago|0 comments
22. 532.▲
    Reducing Memory Access Times with Caches(developers.redhat.com)

    1 points by r4um 11y ago|0 comments
23. 533.▲
    Caching for a Global Netflix(techblog.netflix.com)

    1 points by r4um 11y ago|0 comments
24. 534.▲
    Staying Afloat: The DROWN Attack and CloudFlare(blog.cloudflare.com)

    2 points by r4um 11y ago|0 comments
25. 535.▲
    I was just asked to crack a program in a job interview(erenyagdiran.github.io)

    2 points by r4um 11y ago|0 comments
26. 536.▲
    Why CSP matters I: Keeping things in sync(blog.ndk.io)

    5 points by r4um 11y ago|0 comments
27. 537.▲
    What success really looks like in open source(medium.com)

    3 points by r4um 11y ago|0 comments
28. 538.▲
    Write Fast, Read in the Past: Causal Consistency for Client-Side Applications(hal.inria.fr)

    3 points by r4um 11y ago|0 comments
29. 539.▲
    Building Google’s Data Infrastructure for Ads [pdf](static.googleusercontent.com)

    1 points by r4um 11y ago|0 comments
30. 540.▲
    Eliminating Large JVM GC Pauses Caused by Background IO Traffic(engineering.linkedin.com)

    4 points by r4um 11y ago|0 comments