Memcached 1.6.0 UDP removal: testing integration without production credentials

Goal

Validate an application’s memcached integration in a sandbox that does not expose production credentials.

Constraints

Memcached 1.6.0 dropped the UDP listener and the –U flag, leaving only TCP (plain or TLS) for the binary and ASCII protocols. Legacy clients that default to UDP will fail to connect unless reconfigured. A proxy can translate UDP to TCP, but adds complexity and latency.

Unresolved Decision

What is the most reliable way to emulate the legacy UDP behavior for integration tests, and how does it impact authentication or TLS support?

Questions

• Can a UDP‑to‑TCP shim (e.g., socat) be used in a test harness to preserve legacy client expectations without exposing real credentials?
• What are the observable latency differences when routing through such a proxy compared to direct TCP connections?
• When TLS is enabled, does the absence of UDP affect SASL authentication flows during integration testing?