What is recommended for HTTP or HTTPS connectors to reduce latency?

What is recommended for HTTP or HTTPS connectors to reduce latency?

• A. Always use HTTP for faster response
• B. Disable security to reduce latency
• C. Use FTP for transfer
• D. Always use HTTPS; the latency is not significantly worse

Answer: (D)

Using HTTPS is recommended because securing data in transit is essential, and with modern TLS and HTTP/2 optimizations, the extra latency is minimal. TLS 1.3 reduces handshake cost and, with HTTP/2, multiple requests can be multiplexed over a single connection, so the impact of encryption on latency is often negligible. In MuleSoft, you can further reduce latency by enabling keep-alive and reusing TLS sessions, and by leveraging infrastructural optimizations like TLS offloading. So always using HTTPS provides the right balance of security and performance in typical deployments. The other options compromise security or are not relevant to HTTP connectors (plain HTTP without encryption or FTP).

Using HTTPS is recommended because securing data in transit is essential, and with modern TLS and HTTP/2 optimizations, the extra latency is minimal. TLS 1.3 reduces handshake cost and, with HTTP/2, multiple requests can be multiplexed over a single connection, so the impact of encryption on latency is often negligible. In MuleSoft, you can further reduce latency by enabling keep-alive and reusing TLS sessions, and by leveraging infrastructural optimizations like TLS offloading. So always using HTTPS provides the right balance of security and performance in typical deployments. The other options compromise security or are not relevant to HTTP connectors (plain HTTP without encryption or FTP).