ℹ️ Two big wins in HTTP/3 are the zero roundtrip handshake and improved congestion control
ℹ️ As HTTP/3 is implemented in userspace, you get these performance benefits even if you haven’t updated (or can’t update) your OS kernel
@alyssa_oss@EnvoyProxy ℹ️ End users who see even more benefit are those on lossier networks (e.g., emerging markets, mobile, IoT use cases)
ℹ️ Adding HTTP/3 support to a proxy, ingress, or API gateway is non-trivial (unlike HTTP/2) due to sophisticated congestion control and cryptography
@alyssa_oss@EnvoyProxy If you want to understand the inner workings of HTTP/3 (and changes from HTTP/2), check out the Wikipedia page:
This image from the page shows the main differences in the stack:
@alyssa_oss@EnvoyProxy ℹ️ HTTP/2 sped up HTTP/1 dramatically – but if you lose one packet on a connection, everything gets stalled until the packet is retransmitted.
ℹ️ This is a fundamental limitation of TCP, so HTTP/3 speeds up HTTP/2 even more by implementing the protocol on top of UDP.
@alyssa_oss@EnvoyProxy This video with @OptimisticRyan and @alyssa_oss from the #KubeCon NA 2021 event is also super useful for understanding the changes, benefits, and challenges of HTTP/3 (and has an animation showing head-of-line blocking! 🚅 🚅 🚅 )
He walks through configuring the @CloudNativeFdn Emissary-ingress and Edge Stack API gateways for HTTP/3 support (these projects are built upon @EnvoyProxy)
The latest @InfoQ DevOps and Cloud InfoQ Trends Report has been published 📊
Key topics:
- Data Observability
- FinOps
- eBPF and WASM
- Supply chain security
- Low/no-code platforms
- "Developer Experience as Decision Driver”
Read on to learn more 🧵 👇
@InfoQ Every year, several @InfoQ editors and members of the community get together to share their opinions on the current state of the DevOps and cloud space.
We aim to track the diffusion of technologies, methodologies, and topics in this space
Here is our current take:
@InfoQ The model we use is taken from @geoffreyamoore's diffusion of innovation & "Crossing the Chasm" ⛰️
As pointed out by @swardley, we shouldn't confuse diffusion and evolution (the linked thread provides more context and highlights the value of mapping)
- Everyone is building a platform, whether they realize it or not
- Platform as product FTW 🚀
- Getting exec/C-level buy-in is challenging
- Platform Product Manager will be a hot role 📈
- Balance devex, CLI, UIs, & IaC ⚖️
🧵👇
1/ Everyone is building a platform, whether they realize it or not 🤔
There was a real mix of platform tech at the event:
- Kubernetes
- Serverless
- On-prem
One key theme: every "platform" helped devs to code, ship, and run, reducing toil and increasing speed and safety 🚀 ⛑️
A lot of (successful) platform builds and adoption appeared to be driven bottom-up by developers 🧰
And yes, even that janky "setup-local-dev. sh" script and clumsily assembled GitHub Actions building and deploying from your repo onto an EC2 instance count as a platform 😁
#KubeCon EU Takeaway 2: ➡️ Platforms and “golden paths” enable productivity and reduce developer friction
I saw several great talks, and also presented on why I think golden paths and platform engineering are the next big thing 🔥
Let's explore this in more detail: 🧵 👇
The first mention of "golden paths" was from @MercedesBenz in the opening keynote, where they talked about the K8s-based platform they had built over the past 7 years 🏎️
Lots of thought, effort, and iteration had been applied to the dev experience 🧰
@MercedesBenz Golden paths are all about making it easy for a developer to code, ship, and run applications; to go from biz idea, to code, to test, to running in prod, to collecting telemetry to enable iteration ⚡
There can be one golden path or many, depending on your use cases 🛣️
1. Cloud education is vitally important 2. Platforms and “golden paths” enable productivity 3. Developer experience is top of mind 4. Cloud networking is simplifying 5. Increasing focus on security
Let's explore 1 in more detail 🧵 👇
First, the complete #KubeConEU summary blog post that provides in-depth coverage can be found here: