A particular due to the engineers who shared their story with me and have helped carry this weblog put up to life: Ravi Nagayach<\/a>, Prashant Singh<\/a>, Kshitij Gupta<\/a>, and all the Lambda networking staff. These are of us doing the invisible engineering that retains AWS operating.<\/em><\/p>\n Most infrastructure enhancements at AWS occur invisibly. Engineering groups spend years incrementally rebuilding programs that tens of millions of shoppers depend upon, whereas these programs proceed operating at full scale with out disruption. Marc Olson described this as changing a propeller plane to a jet whereas it\u2019s in flight. One mistake and the airplane goes down. However get it proper\u2026 and nobody notices.<\/p>\n That is the work that can by no means make headlines or get a weblog put up (no less than not when issues go as deliberate). Work like optimizing iptables guidelines, working round kernel lock competition, or rewriting packet headers. The place success is silent. The reward is figuring out what you\u2019ve labored on is best right now than it was per week in the past, and that the subsequent staff gained\u2019t run into the identical constraints you simply eliminated.<\/p>\n I\u2019ve been eager about this lots these days. There are massive launches like S3 Information, which remedy very seen buyer issues, after which there may be the work that\u2019s simply as spectacular that occurs quietly, over lengthy intervals of time, and simply out of sight of our prospects. Immediately, I need to share a Lambda story with you that\u2019s spanned the higher a part of a decade, and that\u2019s made issues we thought unattainable, akin to operating latency delicate workloads in a serverless operate, effectively, doable. It\u2019s the story of Lambda\u2019s networking staff, and the way their delicate inventiveness has each remodeled what\u2019s doable with Lambda and impacted how and what we are able to construct throughout AWS.<\/p>\n![\"XKCD](\"\/images\/xkcd-2259.png\")