Streaming

Every Platform Picked a Side Two API changes, six weeks apart, tell you everything about where the AI agent war in messaging is heading. On December 31, 2025, Telegram shipped Bot API 9.3 with a new method called sendMessageDraft — “allowing partial messages to be streamed to a user while being generated.” A first-class streaming primitive, designed explicitly for LLM traffic, available to every developer with a bot token. On January 15, 2026, Meta’s updated WhatsApp Business terms took effect: general-purpose AI assistants are banned from the WhatsApp Business API. ChatGPT, Perplexity, and every other horizontal assistant that had been quietly building distribution on WhatsApp had to leave. ...

Why Stream at All The traditional Spring MVC model serializes the entire response into memory before sending it. A controller returns a List<Message>, Jackson converts it to a JSON array, and the framework writes the complete byte buffer to the socket. This works until the dataset is large, the source is slow, or both. Consider a database query that returns 10,000 rows. The blocking approach loads all rows into a List, serializes the entire JSON array, and only then begins writing to the client. Memory usage spikes, time-to-first-byte suffers, and the client waits for the slowest row before seeing anything. ...