why libraries like OkHttp or Apache HttpClient are used even though Java has a built-in HTTP client.

Let’s go deep into why libraries like OkHttp or Apache HttpClient are used even though Java has a built-in HTTP client.

---

1️⃣ Java Built-in HTTP Clients

Before Java 11

• java.net.HttpURLConnection
• Low-level API
• Clunky to use for anything beyond basic GET/POST

URL url = new URL("https://api.example.com");
HttpURLConnection conn = (HttpURLConnection) url.openConnection();
conn.setRequestMethod("GET");
int status = conn.getResponseCode();

❌ Problems:

• Verbose code for headers, body, method types
• No easy support for timeouts, retries, connection pooling
• Streaming request/response is not intuitive

---

Java 11+

• java.net.http.HttpClient added
• Better API (async requests, CompletableFuture)

HttpClient client = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://api.example.com"))
    .GET()
    .build();
HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());

✅ Much better, but still lacks some advanced features out-of-the-box.

---

2️⃣ Why use OkHttp or Apache HttpClient

Even with built-in clients, these libraries are preferred in real-world enterprise apps.

Top Reasons:

Reason	Details
Connection pooling	Reuse TCP connections for multiple requests → improves performance
Automatic retries	Retry on transient failures (network glitches, timeouts)
Timeout management	Fine-grained control over connect, read, and write timeouts
Streaming and large bodies	Efficient request/response streaming
Synchronous + Asynchronous calls	OkHttp provides callbacks or Futures for async execution
Interceptors / Filters	Add logging, auth headers, compression transparently
HTTP/2 & SPDY support	Built-in support in OkHttp; built-in client added HTTP/2 later

---

3️⃣ Example: OkHttp

OkHttpClient client = new OkHttpClient();

Request request = new Request.Builder()
    .url("https://api.example.com")
    .addHeader("Authorization", "Bearer token")
    .build();

Response response = client.newCall(request).execute();
System.out.println(response.body().string());

✅ Features:

• Simple syntax
• Easy header management
• Connection pooling automatically
• Supports async enqueue() with callbacks

---

4️⃣ Example: Apache HttpClient

CloseableHttpClient client = HttpClients.createDefault();
HttpGet get = new HttpGet("https://api.example.com");
CloseableHttpResponse response = client.execute(get);
System.out.println(EntityUtils.toString(response.getEntity()));

✅ Features:

• Rich configuration for retries, timeouts
• Support for proxy, cookies, redirects
• Better for enterprise-grade HTTP clients

---

5️⃣ Interview Answer

“Java’s built-in HTTP clients work for basic use cases, but libraries like OkHttp or Apache HttpClient provide advanced features out-of-the-box: connection pooling, retries, streaming, interceptors, timeouts, and HTTP/2 support. They reduce boilerplate and make real-world API integration faster and more reliable.”

---

💡 Key note: Even though Java 11+ has HttpClient, OkHttp is still preferred in Android and high-performance apps, and Apache HttpClient is widely used in legacy enterprise projects.