Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jmUse ALB auth to add user authentication2020-01-27T15:59:09+00:00
https://cloudonaut.io/how-to-secure-your-devops-tools-with-alb-authentication/?ck_subscriber_id=512829374
jmaws alb authentication load-balancers openid google saml authhttps://pinboard.in/https://pinboard.in/u:jm/b:4cb0e4a66ade/Rethinking Netflix’s Edge Load Balancing – Netflix TechBlog2018-10-02T11:43:13+00:00
https://medium.com/netflix-techblog/netflix-edge-load-balancing-695308b5548c
jmnetflix scaling scalability jsq load-balancing load-balancers algorithms distributed-systems architecture opshttps://pinboard.in/https://pinboard.in/u:jm/b:5e6299bd9bb6/DHCPLB: An open source load balancer | Engineering Blog | Facebook Code2016-09-19T11:12:53+00:00
https://code.facebook.com/posts/1734309626831603/dhcplb-an-open-source-load-balancer/
jmfacebook golang go intern dublin dhcp dhcplb load-balancershttps://pinboard.in/https://pinboard.in/u:jm/b:0d7561b04213/Neutrino Software Load Balancer2016-02-18T14:49:52+00:00
http://neutrinoslb.github.io/
jmnetty scala ebay load-balancing load-balancers url http architecturehttps://pinboard.in/https://pinboard.in/u:jm/b:793be14e0ab4/Seesaw: scalable and robust load balancing from Google2016-01-30T19:24:46+00:00
http://google-opensource.blogspot.ie/2016/01/seesaw-scalable-and-robust-load.html?m=1
jmAfter evaluating a number of platforms, including existing open source projects, we were unable to find one that met all of our needs and decided to set about developing a robust and scalable load balancing platform. The requirements were not exactly complex - we needed the ability to handle traffic for unicast and anycast VIPs, perform load balancing with NAT and DSR (also known as DR), and perform adequate health checks against the backends. Above all we wanted a platform that allowed for ease of management, including automated deployment of configuration changes.
One of the two existing platforms was built upon Linux LVS, which provided the necessary load balancing at the network level. This was known to work successfully and we opted to retain this for the new platform. Several design decisions were made early on in the project — the first of these was to use the Go programming language, since it provided an incredibly powerful way to implement concurrency (goroutines and channels), along with easy interprocess communication (net/rpc). The second was to implement a modular multi-process architecture. The third was to simply abort and terminate a process if we ended up in an unknown state, which would ideally allow for failover and/or self-recovery.
]]>seesaw load-balancers google load-balancing vips anycast nat lbs go ops networkinghttps://pinboard.in/https://pinboard.in/u:jm/b:b4e179914043/ELS: latency based load balancer, part 12015-12-09T14:28:29+00:00
https://labs.spotify.com/2015/12/08/els-part-1/
jmELS measures the following things:
Success latency and success rate of each machine;
Number of outstanding requests between the load balancer and each machine. These are the requests that have been sent out but we haven’t yet received a reply;
Fast failures are better than slow failures, so we also measure failure latency for each machine.
Since users care a lot about latency, we prefer machines that are expected to answer quicker. ELS therefore converts all the measured metrics into expected latency from the client’s perspective.[...]
In short, the formula ensures that slower machines get less traffic and failing machines get much less traffic. Slower and failing machines still get some traffic, because we need to be able to detect when they come back up again.
]]>latency spotify proxies load-balancing els algorithms c3 round-robin load-balancers routinghttps://pinboard.in/https://pinboard.in/u:jm/b:067ff62fa178/'Join-Idle-Queue: A Novel Load Balancing Algorithm for Dynamically Scalable Web Services' [paper]2014-08-25T14:39:37+00:00
http://research.microsoft.com/pubs/153348/idleq.pdf
jmWe proposed the JIQ algorithms for web server farms that are dynamically scalable. The JIQ algorithms significantly outperform the state-of-the-art SQ(d) algorithm in terms of response time at the servers, while incurring no communication overhead on the critical path. The overall complexity of JIQ is no greater than that of SQ(d).
The extension of the JIQ algorithms proves to be useful at very high load. It will be interesting to acquire a better understanding of the algorithm with a varying reporting threshold. We would also like to understand better the relationship of the reporting frequency to response times, as well as an algorithm to further reduce the complexity of the JIQ-SQ(2) algorithm while maintaining its superior performance.
]]>join-idle-queue algorithms scheduling load-balancing via:norman-maurer jiq microsoft load-balancers performancehttps://pinboard.in/https://pinboard.in/u:jm/b:b74aa5e37b49/Load Balancer Testing with a Honeypot Daemon2013-12-15T21:53:36+00:00
http://mauveweb.co.uk/posts/2013/12/load-balancer-testing-with-honeyd.html
jmload-balancers ops devops sysadmin testing unit-tests networking honeypot infrastructure bddhttps://pinboard.in/https://pinboard.in/u:jm/b:ec3e58616297/