HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs

Otavio Santana
@otaviojava
HTTP / 1, HTTP /
2 and HTTP / 3:
Past, present and
the future of
APIs
Roan Brasil
@roanbrasil

Otavio Santana
@otaviojava
DevRel Engineer
+ Java Champion
+ JCP-EC-EG-EGL
+ Apache Committer
+ Eclipse Committer
+ Eclipse Project Leader
+ Book and blog writer
Speaker

Roan Brasil
@roanbrasil
Senior Engineer
+ JCP-Member
+ Open Source Contributor
+ Book and blog writer
+ Teacher
Speaker

History of HTTP
The Past, The Present and the Future
HTTP 0.9 HTTP 1.0 HTTP 1.1 HTTP 2 HTTP 3
1991 1996 1999 2015 2018
PAST PRESENT FUTURE

Three-way handshake - TCP Protocol
Sync
Sync/ACK
ACK
Response
Request

HTTP
● Resources
● client-server

How it works
● Method
● Path
● Version of the protocol
● Headers
● Cache

HTTP
● Resources
● client-server
GET / HTTP/1.1
Host: developer.mozilla.org
Accept-Language: fr
HTTP/1.1 200 OK
Date: Sat, 09 Oct 2010 14:28:02 GMT
Server: Apache
Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT
ETag: "51142bc1-7449-479b075b2891b"
Accept-Ranges: bytes
Content-Length: 29769
Content-Type: text/html
<!DOCTYPE html... (here comes the 29769
bytes of the requested web page)

HTTP Status
● 1xx informational response
● 2xx successful
● 3xx redirection
● 4xx client error
● 5xx server error

1XX
● 100 Continue
● 101 Switching Protocols
● 102 Processing (WebDAV; RFC 2518)
● 103 Early Hints (RFC 8297)

2XX
● 200 OK
● 201 Created
● 202 Accepted
● 203 Non-Authoritative Information
● 204 No Content
● 205 Reset Content
● 206 Partial Content
● 207 Multi-Status
● 208 Already Reported
● 226 IM Used

3XX
● 300 Multiple Choice
● 301 Moved Permanently
● 302 Found
● 303 See Other
● 304 Not Modiﬁed
● 305 Use Proxy
● 306 unused
● 307 Temporary Redirect
● 308 Permanent Redirect

4XX
● 400 Bad Request
● 401 Unauthorized
● 402 Payment Required
● 403 Forbidden
● 404 Not Found
● 405 Method Not Allowed
● 406 Not Acceptable
● 407 Proxy Authentication Required
● 408 Request Timeout
● 409 Conﬂict
● 410 Gone

5XX
● 500 Internal Server Error
● 501 Not Implemented
● 502 Bad Gateway
● 503 Service Unavailable
● 504 Gateway Timeout
● 505 HTTP Version Not Supported
● 506 Variant Also Negotiates
● 507 Insufﬁcient Storage (WebDAV)
● 508 Loop Detected (WebDAV)
● 510 Not Extended
● 511 Network Authentication Required

HTTP 1.1 - Rest
REST is acronym for REpresentational State Transfer. It is architectural style
for distributed hypermedia systems and was ﬁrst presented by Roy Fielding in
2000 in his famous dissertation.

Api Design
● API
● Contract First
● Contract Last

Glory of Rest
● Richardson Maturity Model
○ Model of Restful Maturity
○ Integration Problems

Glory of Rest
● Level 0
○ HTTP - transport system for
remote interactions
● Level 1
○ Individual Resources
● Level 2
○ POST
○ GET
○ DELETE
○ PATCH / PUT
● Level 3
○ HATEOAS (Hypertext As The
Engine Of Application State)

HTTP/2
● In 2009, Mike Belshe and
Roberto Peon of Google proposed
SPDY
● HTTP/2 replaces SPDY
● Same semantics HTTP/1.x
● Binary Protocol
● Introduced to improve
performance
● HTTPBis Working Group
○ Speciﬁcation HTTP
○ RFC 7540
○ HPACK - RFC 7541

What is GRPC?
gRPC is a modern open source high performance remote procedure call (RPC) framework
that can run in any environment. Initially developed at Google 2015 using HTTP/2
protocol. Use protobuf as a mechanism for serializing structure data.
https://grpc.io/
https://developers.google.com/protocol-buffers/

Where must I use GRPC?
● Microservices
○ Low-latency and high-throughput communication
○ Strong API contract
● Polyglot environments
● Point-to-Point real time communication
○ Bidirectional streaming
● Network Constrained environments
○ Lightweight message format (mobile application)

HTTP/2 and Java 9
try {
HttpClient httpClient = HttpClient.newHttpClient(); //Create a HttpClient
System.out.println(httpClient.version());
HttpRequest httpRequest = HttpRequest.newBuilder()
.uri(new URI("https://www.google.com/")).GET().build();
//Create a GET request for the given URI
Map<String,List<String>> headers = httpRequest.headers().map();
headers.forEach((k, v) - > System.out.println(k + "-" + v));
HttpResponse < String > httpResponse = httpClient.send(httpRequest,
HttpResponse.BodyHandler.asString());
} catch (Exception e) {
System.out.println("message " + e);
}

Servlet 4.0
@WebServlet(value = {"/http2"})
public class Http2Servlet extends HttpServlet {
@Override
protected void doGet(HttpServletRequest req, HttpServletResponse resp) {
PushBuilder pushBuilder = req.newPushBuilder();
pushBuilder
.path("images/kodedu-logo.png")
.addHeader("content-type", "image/png")
.push();
try(PrintWriter respWriter = resp.getWriter();){
respWriter.write("<html><img src='images/kodedu-logo.png'></html>");
}
}
}

What is RSocket?
RSocket is a binary protocol, bi-directional, multiplexed, message-based based on
Reactive Streams semantics. It provides support for four interaction models. It is transport
protocol agnostic.
https://rsocket.io/

HTTP 3 - The Future
What is new in HTTP 3?
● It is a 3rd version of Hypertext Transfer Protocol (HTTP)
● New protocol speciﬁcation (not ready for production yet)
● Use the same semantics of HTTP/1.* and HTTP/2, such as GET and POST operation
● August-2020 became Internet-Draft

HTTP 3 - QUIC - The Future
QUIC - Quick UDP Internet Connections
● Designed in 2012 by Jim Roskind at Google
● Reduce connection and transport latency
● Multiplexed transport over UDP
● Open source development in Chromium
● Google and Facebook are already using

HTTP 3 - Flupke
String url = "https://platform.sh/";
URI serverUrl = URI.create(url);
HttpRequest request = HttpRequest.newBuilder()
.uri(serverUrl)
.header("User-Agent", "Flupke http3 library")
.timeout(Duration.ofSeconds(10))
.build();
HttpClient client = Http3Client.newHttpClient();
HttpResponse<String> httpResponse = client.send(request,
HttpResponse.BodyHandlers.ofString());
System.out.println("Got HTTP response " + httpResponse);
System.out.println("- HTTP headers: " + httpResponse.headers());

HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs

Similaire à HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs (20)

Dernier

Dernier (20)

HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs