http2 protocol originally is the new version of http1. This network protocol is used by the www (World Wide Web) and it is a huge revision of the first prototype. http2 was made by the Hypertext Transfer Protocol working gathering httpbis (where bis signifies "second") of the Internet Engineering Task Force. The institutionalization exertion was bolstered by the browsers - Chrome, Opera, Firefox, Internet Explorer 11, Safari, Amazon, Edge, etc. Most significant programs included http2 bolster before the finish of 2015.
The protocol makes our applications quicker, less difficult, and more hearty an "uncommon blend" by enabling us to fix a huge number of the http 1.1 workarounds beforehand done inside our apps and address these worries inside the vehicle layer itself. Far and away superior, it additionally opens up various altogether new chances to advance our applications and enhance execution.
The essential objectives for http2 protocol are to lessen inertness by empowering full demand and reaction multiplexing, limit convention overhead through productive pressure of HTTP header fields, and include bolster for ask for the tasks prioritization, server push. To execute these prerequisites, there is a substantial supporting cast of other convention improvements, for example, new stream control, blunder dealing with, and overhaul systems, yet these are the most vital components that each web engineer should comprehend and use in their applications.
http2 does not adjust the application semantics of HTTP in any capacity. All the center ideas, for example, HTTP techniques, status codes, URIs, and header fields, stay set up. Rather, http2 changes how the information is designed (encircled) and transported between the customer and server, both of which deal with the whole procedure, and conceals all the intricacy from our applications inside the new confining layer. Accordingly, all current applications can be conveyed without adjustment.
At fisrt place Google examine the issues with http 1.1 version. At the time, they were burning through a large amount of dollars a year to help their server farms, and the first version convention just cost excessively as far as CPU assets and web association limit. They created SPDY as an exploratory contrasting option to http 1.1 - a convention intended for better security and enhanced page stack times which would be the antecedent to http2
To accomplish the execution objectives set by the HTTP Working Group, http2 presents another twofold encircling layer that is not in reverse perfect with past http1.x servers and customers' thus the real convention form addition to http2.
All things considered, unless you are actualizing a web server (or a custom customer) by working with crude TCP attachments, at that point you won't perceive any distinction: all the, amazing failure level encircling is performed by the customer and server for your benefit. The main perceptible contrasts will be enhanced execution and accessibility of new abilities like demand prioritization, stream control, and server push.
Although in the time, apart from supporters, the protocol also gains a lot of criticism, it has its advantages, which must certainly be taken into account in its use.
You can read more about the HTTP/2 Protocol here: