<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tech Radar Digest — May 2026 on Lê Tuấn Anh — Go Backend Architect &amp; Microservices Engineer</title><link>https://tanhdev.com/radar/2026-05/</link><description>Recent content in Tech Radar Digest — May 2026 on Lê Tuấn Anh — Go Backend Architect &amp; Microservices Engineer</description><image><title>Lê Tuấn Anh — Go Backend Architect &amp; Microservices Engineer</title><url>https://tanhdev.com/vesviet.png</url><link>https://tanhdev.com/vesviet.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://tanhdev.com/radar/2026-05/index.xml" rel="self" type="application/rss+xml"/><item><title>Tech Radar, May 16, 2026: Grok Build Enters the Arena, OpenAI Breaks Azure Exclusivity, Anthropic Goes to Wall Street, and T-3 to Google I/O</title><link>https://tanhdev.com/radar/grok-build-openai-aws-multi-cloud-anthropic-wall-street-google-io-may-2026/</link><pubDate>Sat, 16 May 2026 09:00:00 +0700</pubDate><guid>https://tanhdev.com/radar/grok-build-openai-aws-multi-cloud-anthropic-wall-street-google-io-may-2026/</guid><description>&lt;h1 id="tech-radar-may-16-2026-grok-build-enters-the-arena-openai-breaks-azure-exclusivity-anthropic-goes-to-wall-street-and-t-3-to-google-io">Tech Radar, May 16, 2026: Grok Build Enters the Arena, OpenAI Breaks Azure Exclusivity, Anthropic Goes to Wall Street, and T-3 to Google I/O&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>Executive Summary &amp;amp; Quick Answer&lt;/strong>: Tech Radar, May 16, 2026: Grok Build Enters the Arena, OpenAI Breaks Azure Exclusivity, Anthropic Goes to Wall Street, and T-3 to Google I/O. Architectural analysis highlights performance benchmarks, security guidelines, and operational deployment strategies under 2026 production standards.&lt;/p>
&lt;p>&lt;strong>Key Takeaways&lt;/strong>:&lt;/p></description></item><item><title>Gateway API v1.5 &amp; Ingress2Gateway: The Future of K8s Networking</title><link>https://tanhdev.com/radar/radar-2026-05-01-gateway-api-v1-5/</link><pubDate>Fri, 01 May 2026 07:30:00 +0700</pubDate><guid>https://tanhdev.com/radar/radar-2026-05-01-gateway-api-v1-5/</guid><description>&lt;h1 id="gateway-api-v15--ingress2gateway-the-future-of-k8s-networking">Gateway API v1.5 &amp;amp; Ingress2Gateway: The Future of K8s Networking&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>Executive Summary &amp;amp; Quick Answer&lt;/strong>: Gateway API v1.5 &amp;amp; Ingress2Gateway: The Future of K8s Networking. Architectural analysis highlights performance benchmarks, security guidelines, and operational deployment strategies under 2026 production standards.&lt;/p>
&lt;p>&lt;strong>Key Takeaways&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>Production deployment guidelines and P99 latency optimizations cut overhead by up to 40%.&lt;/li>
&lt;li>Component integration patterns enforce strict fault isolation and state consistency.&lt;/li>
&lt;li>High-concurrency resilience is validated through automated canary gates and circuit breakers.&lt;/li>
&lt;/ul>&lt;/blockquote>
&lt;p>If your ingress layer still depends on a 400-line manifest full of controller-specific annotations, you do not have a clean networking platform. You have institutional memory encoded as YAML archaeology.&lt;/p></description></item></channel></rss>