This week, we discuss Stripe's singularity letter, its $8B Open Router buy, and AI job anxiety. Plus, Matt plays “Bot or Not” on another podcast.

Watch the YouTube Live Recording of Episode 587

Runner-up Titles

• Inertia wins again
• We don’t talk about the Pope very much.
• Better than this year’s storage arrays
• AI pimps its own ride
• Chonking machine
• A lot of chonk opportunity
• I’m tired of tech people being all fancy
• Thanksgiving with Ed Zitron
• No religion, no politics, no AI
• My recommendation: try harder
• Teletubbies for Adults.

Rundown

• Singularity, Models and Routers
  • Scoop: Stripe says "the singularity" has begun
  • Stripe strikes mega-deal for OpenRouter
  • Hugging Face reportedly in talks to be acquired for $13B
  • Routing is coming for the frontier AI labs
  • Terminator Judgement Day: August 29, 1997 2:14 a.m. Eastern Time
• The AI backlash goes mainstream
  • 52% of Americans Now More Concerned Than Excited About AI, With Under-30s Crossing a Majority for the First Time
  • Why Is Everyone In Tech So Sad?
  • The AI Hater's Manifesto
• 40 Years of Infrastructure as Code: Ansible → Terraform → Kubernetes → Crossplane → AI Agents

Relevant to your Interests

• Cursor Origin review: An engineer's perspective
• Claude can now pull data from your browser tabs and keep working on your desktop
• OTel Isn't Going Well (And I Made A Spreadsheet About It)
• Walmart is finally launching Apple Pay support next week
• Broadcom debt deal expected to reach upwards of $70 billion, sources say
• Anthropic-Backed Ode Acquires Casper Studios to Expand Corporate AI Deployments
• OpenAI 'will be a public company in 2027' or sooner, CFO Friar tells employees
• Google Aims to Boost AI With Purchase of Spirit Airlines Data
• The website that created an AI clone of its editor in chief
• OpenAI Jalapeño: Better Than Nvidia Blackwell
• An Inside Look at the Relay Market Powering Token Resellers and Fraud
• Meta settles social media addiction case with California, other states for $16.7 billion
• Hundreds of leaked AWS keys give full control over corporate accounts
• Free Hardened Container Images | Minimus
• Cyber startup Minimus shuts down, returns cash to investors

Nonsense

• Apple Releases New Polishing Cloth
• Jason Kelce promotes mailing pee to data centers, Liquid Death
• Paradox Inc. Movie From Daniel Roher, Lord Miller, Universal In Works

Conferences

• WeAreDevelopers NA, Sept 23-25, 2026, Discount Code: DEVPOD50
  • 25 Free Tickets
• DevOpsDays Graz, Sept 4-5, 2026
• Cloud Foundry Summit, Sept. 21st to 22nd, Heidelberg, Coté speaking.
• DevOpsDays Rockies, Sept. 22 – 23, 2026, Discount Code: 26DODSWEDEFTALK
• DevOpsDays Dallas, Sept 28-29, 2026
• DevOpsDays Vilnius, Sep 30 - Oct 1, 2006, Lithuania.
• DevOpsDays Prague, Oct 5, 2026 - Coté speaking.
• DevOpsDays Istanbul, Oct 24th, 2026, Coté keynoting.
• VMware User Group, Orlando, Oct 20-22, 2026
• Cloud Native Denmark, Nov 19th, 2026, Copenhagen, Coté keynoting.
• Build Stuff, Dec 2-4, 2026, Vilnius, Lithuania.
• cfgmgmtcamp, February 1st to 3rd, 2027, Ghent.
• SCALE 24x Pasadena, CA, April 1-4, 2027

SDT News & Community

• Join our Slack community
• Email the show: questions@softwaredefinedtalk.com
• Free stickers: Email your address to stickers@softwaredefinedtalk.com
• Follow us on social media: Twitter, Threads, Mastodon, LinkedIn, BlueSky
• Watch us on: Twitch, YouTube, Instagram, TikTok
• Book offer: Use code SDT for $20 off "Digital WTF" by Coté
• Sponsor the show
• Sponsor more podcasts with Failover Media

Recommendations

• Brandon:
  • Tuner **
  • Your AI Project Doesn't Need More Agents
• Matt:
  • Tech, Texas & What It Takes to Run a Podcast with Matt Ray | Cyber Chat Ep. 5
  • Line of Duty
  • Anti-pick: Roku’s New Slop Channel
• Coté:
  • Mini MLC, 30L.

Sponsored By:

• WeAreDevelopers US: WeAreDevelopers World Congress North America Sept 23–25, San José, CA Promo Code: DEVPOD50

HTML and Markdown are back in the spotlight, and AI is a big reason why. In this episode of Sync Up, hosts Stephen Rice and Arvind Mishra sit down with Dorine Rassaian (OneDrive Sr. Product Manager) and Nicole Woon (SharePoint Sr. Product Manager) to explore how AI-generated content is driving renewed interest in HTML and Markdown files across Microsoft 365.

Learn how organizations are using HTML dashboards, newsletters, reports, presentations, and interactive experiences generated with AI, and how OneDrive and SharePoint are evolving to make these files easier to view, edit, collaborate on, and share.

The conversation covers:

✅ Why HTML and Markdown are experiencing a resurgence

✅ How AI tools like Copilot generate HTML and Markdown content

✅ New OneDrive experiences for HTML and Markdown files

✅ WYSIWYG editing, inline text editing, and anchor comments

✅ Human-to-agent collaboration and the future of AI-powered work

✅ HTML-powered SharePoint pages and intranet experiences

✅ Real-world examples, dashboards, presentations, newsletters, and more

Whether you're a developer, IT professional, SharePoint administrator, or simply curious about how AI is changing the way we create and communicate, this episode offers a look at the future of content creation in Microsoft 365.

Guests

🎙️ Dorine Rassaian Senior Product Manager, OneDrive

🎙️ Nicole Woon Senior Product Manager, SharePoint

Resources

🔗 OneDrive Blog: https://aka.ms/OneDriveBlog

🔗 OneDrive Office Hours: https://aka.ms/OneDriveOfficeHours

🔗 Microsoft Podcasts: https://aka.ms/MicrosoftPodcasts

APIs are the backbone of modern applications, powering everything from mobile experiences and microservices to AI-driven applications and business-critical integrations. As customers continue to modernize their platforms on Azure, they increasingly expect their API infrastructure to remain available even in the face of datacenter-level disruptions.

With zone redundancy in Standard v2, Azure API Management now enables customers to increase resilience against Availability Zone failures while continuing to benefit from the simplicity, performance, and cost efficiency of the v2 platform.

Why Zone Redundancy Matters

Azure Availability Zones are physically separate locations within an Azure region, each with independent power, cooling, and networking infrastructure. By distributing API Management resources across multiple zones, organizations can reduce the impact of a single datacenter failure and improve service continuity for their APIs. 

Until now, customers who required built-in zone-level resiliency often needed to evaluate higher-end deployment options. With this enhancement, Standard v2 customers can now deploy API gateways across Availability Zones and benefit from improved reliability while maintaining the streamlined operational model of the v2 platform.

What’s New

Zone Redundancy for Standard v2 extends the platform's resiliency by distributing service capacity across multiple Availability Zones within a supported Azure region.

Key benefits include:

• Higher Availability: API traffic continues to flow even if a single Availability Zone experiences an outage.
• Built-in Resiliency: Redundancy is provided at the platform layer, reducing the need for customers to design and manage complex intra-region failover solutions.
• Production-Ready Reliability: Customers can confidently run critical API workloads on Standard v2 with stronger availability guarantees.
• Operational Simplicity: The service automatically manages capacity distribution, health monitoring, and recovery behavior across zones.
• Cost-Effective Resilience: Customers gain zone-level protection without requiring an enterprise-tier deployment model.

Built on the Modern v2 Platform

The v2 platform was designed from the ground up to provide a faster, more reliable, and more scalable API Management experience. Standard v2 already delivers capabilities such as rapid deployment, simplified networking, workspace support, and flexible scaling. Zone Redundancy further strengthens the platform by expanding its reliability story for production workloads. 

This announcement builds on our broader investment in making Azure API Management more accessible to a wider range of organizations, from digital-native startups to large enterprises modernizing their application estates.

Ideal Scenarios

Zone Redundancy in Standard v2 is particularly valuable for customers who:

• Run business-critical APIs that must remain available during datacenter incidents.
• Consolidate multiple application workloads behind a single API gateway.
• Expose APIs consumed by mobile, partner, and customer-facing applications.
• Support AI applications and agent-based architectures that depend on highly available API endpoints.

For organizations adopting modern cloud and AI native architectures, this capability helps ensure that API infrastructure remains aligned with broader application resiliency strategies.

A Foundation for Reliable AI and API Platforms

As AI-powered applications continue to proliferate, APIs increasingly become the critical connection layer between models, agents, business systems, and data platforms. Downtime at the API layer can have a direct impact on application availability, customer experience, and business operations.

By bringing zone redundancy to Standard v2, we are making it easier for organizations to build highly resilient API platforms that can serve as the foundation for next-generation AI and digital transformation initiatives.

Getting Started

Zone Redundancy for Standard v2 can be enabled in supported Azure regions, allowing customers to deploy API Management with built-in protection against Availability Zone failures.

We recommend reviewing your application's overall resiliency architecture, including backend redundancy, traffic management, and disaster recovery requirements, to maximize the benefits of zone-resilient API infrastructure.

Enable Zone Redundancy in the Azure Portal

Getting started with Zone Redundancy in Azure API Management Standard v2 is straightforward and can be configured during service creation.

Create a New Standard v2 Instance with Zone Redundancy

1. Sign in to the Azure portal.
2. Select Create a Resource and search for Azure API Management.
3. Choose Standard v2 as the service tier.
4. Select a region that supports Availability Zones.
5. In the Availability Zones section, enable Zone Redundancy.
6. Review and create the service.

After deployment, Azure API Management automatically distributes service capacity across multiple Availability Zones within the selected region, helping maintain API availability during a zone-level outage.

Looking Ahead

This release represents another step in our ongoing investment in the Azure API Management v2 platform. We remain committed to delivering the reliability, scalability, security, and developer experiences that organizations expect from a modern API management service.

We are excited to see what our customers build with a more resilient Standard v2 platform and look forward to your feedback as you continue modernizing and scaling your API ecosystems on Azure.

Learn more by visiting the Azure API Management documentation and exploring the latest reliability guidance for API Management deployments.

In high-throughput microservices, real-time gaming engines, and financial computing systems, minimizing managed heap allocations is one of the most effective strategies for eliminating Garbage Collection (GC) pauses and maximizing application throughput.

As of today, the stable production foundation powering enterprise software is C# 14 running on .NET 10, while preview releases for C# 15 and .NET 11 continue to advance the runtime. In this practical technical guide, we explore zero-allocation idioms, span-based buffer slicing, SIMD-accelerated searches, and frozen collections to help you write high-performance C# code.

Table of Contents

• The Zero-Allocation Imperative in Cloud-Native .NET 10
• Slicing Memory without Heap Overhead - Spans, ReadOnlySpans, and MemoryMarshal
• Stack Allocation, Ref Structs, and Generic Anti-Constraints
• High-Speed String and Buffer Searching with SearchValues
• Sub-Nanosecond Lookup Caching - FrozenSet and FrozenDictionary
• Frequently Asked Questions (FAQ)

public class LegacyHeaderParser
{
    // Allocates multiple new string objects on the managed heap for every parsed header
    public (string Scheme, string Host) ParseAuthorization(string authHeader)
    {
        int spaceIndex = authHeader.IndexOf(' ');
        if (spaceIndex == -1) return (string.Empty, string.Empty);

        string scheme = authHeader.Substring(0, spaceIndex); // Heap Allocation 1
        string token = authHeader.Substring(spaceIndex + 1);  // Heap Allocation 2
        return (scheme, token);
    }
}

using System;

public class HighPerformanceHeaderParser
{
    // Zero heap allocations! Slices memory in place on the stack
    public bool TryParseAuthorization(ReadOnlySpan<char> authHeader, out ReadOnlySpan<char> scheme, out ReadOnlySpan<char> token)
    {
        int spaceIndex = authHeader.IndexOf(' ');
        if (spaceIndex == -1)
        {
            scheme = default;
            token = default;
            return false;
        }

        scheme = authHeader.Slice(0, spaceIndex);        // 0 bytes allocated
        token = authHeader.Slice(spaceIndex + 1);       // 0 bytes allocated
        return true;
    }
}

Stack Allocation, Ref Structs, and Generic Anti-Constraints

When temporary scratchpad memory is required during parsing or mathematical transformations, allocating a byte array (new byte[256]) forces a heap allocation. Modern C# allows developers to allocate small temporary buffers directly on the execution stack using stackalloc.

 

Because stack-allocated buffers are automatically cleaned up when the containing method frame exits, they bypass the Garbage Collector entirely.

 

 

Zero-Allocation Hex Encoding with stackalloc

public static class FastEncoder
{
    public static string ToHex(ReadOnlySpan<byte> bytes)
    {
        // Allocate temporary char buffer on the stack (max 512 chars)
        Span<char> hexBuffer = stackalloc char[bytes.Length * 2];
        const string hexAlphabet = "0123456789ABCDEF";

        for (int i = 0; i < bytes.Length; i++)
        {
            byte b = bytes[i];
            hexBuffer[i * 2] = hexAlphabet[b >> 4];
            hexBuffer[i * 2 + 1] = hexAlphabet[b & 0x0F];
        }

        // Only one heap allocation: the final returned string
        return new string(hexBuffer);
    }
}

The 'allows ref struct' Anti-Constraint

In modern C#, the allows ref struct generic constraint enables ref struct types (like ReadOnlySpan<T>) to be used as generic type arguments in interfaces and delegate handlers without violating stack safety rules:

 

public interface ISpanProcessor<T> where T : allows ref struct
{
    void Process(T data);
}

public class FastBufferHandler : ISpanProcessor<ReadOnlySpan<byte>>
{
    public void Process(ReadOnlySpan<byte> data)
    {
        // Process stack-bound data efficiently
    }
}

This capability allows enterprise architectures to build highly abstracted, reusable pipelines while preserving zero-allocation performance guarantees.

using System;
using System.Buffers;

public class HighSpeedSanitizer
{
    // Pre-computed SIMD search structure initialized once at startup
    private static readonly SearchValues<char> s_invalidUrlChars = 
        SearchValues.Create("\"<>\\^`{|}[] ");

    public static bool ContainsInvalidUrlCharacters(ReadOnlySpan<char> urlSegment)
    {
        // Executes vectorized SIMD hardware instructions: up to 10x faster than foreach!
        return urlSegment.ContainsAny(s_invalidUrlChars);
    }
}

using System.Collections.Frozen;
using System.Collections.Generic;

public class RouteConfigManager
{
    // Frozen during application startup: optimized exclusively for blistering-fast reads
    private static readonly FrozenDictionary<string, int> s_routeWeights = 
        new Dictionary<string, int>
        {
            ["/api/v1/users"] = 10,
            ["/api/v1/orders"] = 25,
            ["/api/v1/payments"] = 50,
            ["/api/v1/analytics"] = 5
        }.ToFrozenDictionary(StringComparer.OrdinalIgnoreCase);

    public static int GetRouteWeight(string path)
    {
        return s_routeWeights.TryGetValue(path, out int weight) ? weight : 0;
    }
}

High-performance C# engineering empowers developers to extract maximum throughput and predictability from modern hardware without sacrificing code clarity or memory safety. By incorporating spans, stack allocations, SIMD search utilities, and frozen collections into your daily engineering practices, you can build enterprise applications that handle massive traffic with near-zero latency overhead.

Take time this week to profile your core service endpoints using BenchmarkDotNet, identify your most frequent heap allocations, and refactor hot parsing loops into zero-allocation span pipelines.

Which zero-allocation C# technique or modern collection type has delivered the biggest performance improvement in your codebase? Share your benchmarks, experiences, and questions in the comments section below!