Why System.IO.Pipelines (the engine behind ASP.NET Core Kestrel) beats traditional Stream and byte[] buffers:

• Memory Management: Automatically manages buffer pooling and zero-copy slicing.
• Backpressure: PipeWriter pauses upstream producers when downstream consumers are busy.
• Line/Packet Parsing:

while (true)
{
    ReadResult result = await reader.ReadAsync();
    ReadOnlySequence<byte> buffer = result.Buffer;
    while (TryReadLine(ref buffer, out ReadOnlySequence<byte> line))
    {
        ProcessLine(line);
    }
    reader.AdvanceTo(buffer.Start, buffer.End); // Tells pipeline which bytes were consumed!
    if (result.IsCompleted) break;
}

System.IO.Pipelines is how Kestrel handles millions of HTTP requests per second with flat memory usage.

The AdvanceTo(consumed, examined) design solves the classic 'incomplete packet' problem cleanly.