What is REST API? | REST API Tutorial | REST API Concepts and Examples | Edureka

Since the invention of the Internet, we have been using different applications on web pages to obtain data from various resources. However, have you ever thought about where this data comes from? Well, it is from the server that we get the data from. Hello everyone, this is Sahiti on behalf of Edureka and I welcome you to this session on “What is REST API?” So the session will mainly focus on how a client communicates with the servers to extract the required information. So without wasting any time let's take a look at the topics of today's session, so we start a session by understanding the need of REST API and then we discuss

what

is REST API, then I will talk about the features of REST API. and then I will delve into the principles of the REST API.

Finally, I will tell you about the REST API methods and then I will end the session by telling you how you can implement the REST API or how you can create a REST API, so I hope the agenda is clear. Alright guys, before we continue with the session, I would like to ask everyone who is inte

rest

ed in knowing about the top trending technologies to subscribe to our direct channel to receive daily notifications about various

concepts

of the top trending technologies . let's start with the first topic of today's session, that is why we need the REST API.

Now consider a scenario where you are using the app to book my show. I am sure you all know that you must use book minds your app on a regular basis by now, obviously when you use this app you must have observed that you know that the app needs a lot of input data as the data present in the application are never static, so

what

I mean by that is when you consider the book: your application. all the time movies are updated daily even show times and places where movies are screened or maybe not only regarding two movies but also regarding events the data is updated periodically so where?

Do you think we get this data? Well, this data is received from a server or more commonly known as a web server, so the client requests the required information from the server, why an API and then the server sends a response to the plane here. the response sent to the client is in the form of an HTML web page. Now, do you think this is the appropriate response you would expect when you send a request to the server? Obviously it is not correct. Imagine if you are searching for data for a specific movie at a specific place and at a specific time, do you expect an HTML page to be returned as a response?

Well, I guess I would also say an "Oh right" since I would also prefer the data to be returned in the form of a structured format rather than a full web page. The data returned by the server in response to the client's request is in JSON format or in XML format now the Jason and XML formats are sent because you know they have a suitable structure in which the data is represented now if I talk about the JSON format and the XML format, as you can see on my screen, for example let's say that We want to know the details of the movies they are. coming soon in a specific city, so what you can do is simply send a request for this particular information to the client, the server returns the data in JSON or XML format so that the JSON format is displayed as best as it can.

I see on my screen so basically there is a city and then there are categories of movies and in the category that will appear soon, when you get to the XML format in the XML format section, basically you have movies of cities and then again we have a category section which shows Coming soon, if you notice that the JSON format is basically the format of an object where you know that the values ​​of the object are returned to the user, and coming to the XML format, the XML format follows a hierarchical data structure in which the data They can be returned now.

This sounds quite simple but the only problem that is present in this framework is that you know that you have to use many methods to get the required information from the server even if the data is returned in a simple format which is JSON or XML formatted. , the only problem so far is that you have to work a lot to get your data back, as you know you have to do a lot of pauses to get methods and then you have to request the data to be returned and so on for a single piece of information, this sounds good, but imagine the scenario where you continuously search for data and then have to search for so many methods now, this obviously becomes cumbersome now to avoid those kind of scenarios that appeared in the picture. the REST API, so the REST API creates an object and then sends the values ​​of the object in the generators to the client requests.

Now that you know the REST API is next, let's see what exactly the REST API is and what the List API is. Now, as I just mentioned, breaths are just the fact that you can simply create an object with the data requested by the client and then send the values ​​of the object in response to the user. Now let's say you know if you want to discover a scenario. of a specific movie, let's say you know if Infinity Ward is showing in Hyderabad at the specific place, let's say you know an IMAX and then timing at 10, 13 and 9, let's say if we want to find out this particular data to find out in particular. data, what will happen is that a client will send the request to the server and yes, it wants to find out the data that you know that the movie Infinity Ward is showing in the city hives or in IMAX at 10:30 or not, when the application is submitted. is sent to the server, what it allows the API to do is let you know that it creates an object from this particular request and then it finds out if it knows that it is played or not, so it looks up the data on the server for the types of request if you find them. outside, you know that if the data is present, it just sends a response to the client with the values ​​of that particular object, so now if you look here what's happening, you're creating an object and then you have some values ​​of the object and what is.

What happens is that the values ​​of the object are sent to the client, so basically the state of an object is sent to the client, so every time there is no need to generate a new object, so the new thing that happens is simply passing the state of an object to the client, so since you're simply passing the state of an object, that's where the term representational state plants comes in. If I have to define

rest

for you, then presentation or rest state transfer is an architectural style like In addition to an approach for communication purposes that is often used in the development of various web services, this rest architectural style helps to take advantage of lower bandwidth usage to make an application more suitable for the Internet and is often considered the language of the Internet and is completely based. in resources apart from this it is also a stateless client-server model that you can understand so the rest is really simple guys it is just an architectural style as well as an approach for communication purposes that is often used in various web service developments so now that you know what is rest let's look at the features of REST API so the features of REST API are as you can see on my screen it is simpler it has proper documentation and it gives you proper logging of error messages, before the rest.

Enter the picture what we had was like this, after the REST API took over the world, you can just say you know you can use the REST API in a much easier way than getting to the documentation, so it comes with a good documentation so that you understand each and every step of how you can create a REST API using various technologies, frameworks and how you can integrate them in your applications and finally, you get error messages when I say error messages, it has information Proper recording of errors, for example. Let's say you know that you are creating a REST API using a specific framework and then you are stuck somewhere, what happens is that you get a proper message about the error that appears so that the user can understand what the error is about and get the chocolate bar.

These were the features of REST API. Now let's move forward and understand the principles of REST API. There are six clown principles established by Dr. Fielding who would like to define REST API design in 2000, so the six counting principles are layered systems of stateless uniform client-server interface and on-demand code, for What when talking about stateless, what I mean by stateless is that when requests are sent from a client to the server, it contains all the information necessary for it to be understood, so it can be part of a URL or the body of query string parameters or even headers.

Now the URL is basically used uniquely. I didn't find that the source and body maintain the state of the requesting resource once the server does the processing a proper response is sent to reject via the header or response state which reaches the client/server as I said client-server what do I mean by that? To start with, you know that you have a uniform interface that separates the clients from the server, so separating the concerns basically helps improve the portability of the user interface across multiple platforms as well as to improve the scalability of the server components by arriving at a uniform interface to obtain uniformity in the rest of the application has been defined for interface constraints which are resource identification, source manipulation using representations, self-describing messages and Hypermedia as the engine of application state, becoming cacheable to provide better performance, applications are often made as cacheable, it is done through tagging. the server response as collectible or non-collectible, whether implicitly or explicitly, if the response is defined as collectable, then the client cache can be reused to generate data for equivalent responses in the future.

It also helps prevent reuse of stolen data in the next step. Moving forward with layered systems, layered system architecture allows an application to be more stable by limiting the behavior of components. This architecture enables load balancing and provides shared caches to promote scalability. The layered architecture also helps improve application security, since the components of each layer cannot interact beyond each other. the next immediate layer is and finally it gets to the on-demand code. The on-demand kernel is an optional constant and is used as little as possible. Allows you to download and extend a customer score or application list.

The interface will be used within the application in essence. This simplifies customers by creating a smart application that does not depend on its own code structure. Now that you know the principles behind the REST API, let's next take a look at the methods of the best API that all of you could be working with. Web technologies, what do you do? You work on raw applications. When I say raw I mean you know we create a resource, we read the source, we update a resource and we delete a resource now, for example, if you consider the URL. which you can see on my screen what it says is you know HTTP and then book my coastal communication barra now Adar barra movies if you watch here for quite a while I've been saying the word resource, do you know what it means?

Well, the resource is basically what you want to do, so for example, let's say you know we want to search for the city in Noida and then movies, so if you consider the URL that you can see on my screen if you hadn't put it like that. then you would have searched for it as if you know the search is equal to noida and then you would put one more query parameter of movies, so basically you would have to put the query parameters which are Noida and movies and before that you had to put the URL, but obviously that doesn't sound like a resource, because you can't always just put a question mark and then you can't keep putting the query parameter instead, you can use these URLs like you know, with the forward slash you mentioned the first parameter and with the second diagonal slash. you mentioned the second parameter and so on, that's basically how your data structure could also be defined on the server, so that's what I basically mean by a resource, so when I say source, source is something that a client want to know or maybe the data that the client is looking for in Word, so now to perform these actions, which are basically create a resource, read from the source, update and delete the resource, you can actually use the HTTP methods, which They are nothing more than the REST API methods, to create a request. you can use the post method to read a request, you can use the get method to update a resource, you can use the put method and to delete a resource you can use the delete method, so all these methods together are basically theHTTP methods, that is, post, put and delete are the HTTP methods, so now that you know what the Leste API is and everything you need to take into account to offer an efficient application, let's see below how you can create a REST API, so for this hands on demo what I'm going to do is create a simple and raw List app using Nights so to build the app basically I'm going to use expressjs without jails, Joey and note born other than that let me tell you know that I will do that.

I will be using the Webstorm ID to write and run the codes so you can use any ID as per your convenience, so let's start by creating our REST API using node.js, so what I am going to do is basically create a project directory that you know I'm going to have all the files related to the project so let's say you know I just right click here and then let me create a project directory, let's say a demo for West API now basically this project directory is initially blank. as you can see on my screen but after some time once you install all the necessary libraries and packages you will see that it knows the dot package, the JSON file and the package locks that automatically created JSON file.

I'm going to open up my command prompt and then what I'm going to do is I'm going to go to my demo folder, so if you notice here, my demo folder was an e directory and the name is demo forest API, so what I'm going to do is I'm going to type E and colon here and then the unmentioned CD. and type demo for the rest API correctly so that I will automatically never access my project folder via command prompt. Now what you have to do is install node.js first to install node.js, it's really simple. to go to its official website and then you have to choose the LTS version depending on what your pet is, like Windows 32 bit or 64 or maybe other versions, depending on that you download your version, double click on it and it will automatically install the node, so since I already installed node on my system.

I'll just open the version and show it to you as I type node - - version, you can clearly see that I have version 10 points 16 points, oh, that means our node is installed now. What we have to do is basically call the NPM package to initialize the NPM modules on your system, so to do that, what it will do is write NPM to it, so this will basically initialize all the NPM modules on your system once . you do this, what you see is basically you will be asked to enter your project details, for example let's say the package name will be a demo, oh it says you can't write capital letters correctly so I'll write the demo here . and then the version will just be 1.0 point so I'll just click enter description let's say we mentioned that it's handy for creating the REST API after that entry point this is the main thing that you basically have to enter so remember the fact. that you have to mention the entry point file so here I am going to mention that it is a script or a change so this is basically from where our process workflow will start and then we just click enter and then I will see that you have the test command.

I will just click on enter get repository, enter keywords, enter author, let's say I put my name and the lysis will be the same, after that it will ask you for confirmation, so basically the project name will be demo version 1.0 0.0 description which will be hand stitched for the creation of the main REST API to be script or claps and so on, if that's okay, I'll just click Y and enter, so what you define so far is basically the metadata for your project, so if I go back now, you'll automatically see that you know the package file has been created.

Now, if I go back to my command prompt, what I have to do is then install Express or J's to install Express or J's. what you have to do is mention npm i and then mention the name of the library which is express so you automatically see that you know it's being downloaded so let's wait for it to install so express is basically a web framework that can be used together with node.js, so this is a web framework that allows you to create a relaxing API with the help of helper methods, middle layers to configure your application, after that, similarly you will have to install Joey to install Joey.

I'll write NPM I J oh I write so I once mentioned that you'll see you know the Joey library is also being installed. Joey is basically used to validate your information, whether it is in the correct format or not, so that you don't have to validate all the time. on your server you can directly install this library and this library will validate the information for you. After that, you also need to install node one. To do this, what I will do is type NPM I - G. mention note 1 and click enter so you can see that note 1 is also being installed, so let's wait for that to happen again.

As you can see, Nordman is also installed now. Note one is basically used to watch all the files with any type of extension present in the folder which is basically the project folder also with note 1 on watch you don't have to restart the node.js server every time changes so basically what usually happens is if you don't use note 1 then you have to restart that server every time you make a change so with the help of node 1 you don't have to do it automatically. Node 1 will implicitly detect the changes and then restart the server once now. you're done installing all these frameworks, let me open the package in the adjacent file and show you, so if I open the JSON dot file from the package with webstorm, okay, let me zoom in a little bit so you can see when I open. my package to JSON file, what you see clearly is the metadata that you entered when you were initializing your npm module, so that's basically the demo and description and then it was the main file etc, it was package to JSON file.

Guys, now what you have to do is basically define the entry point for your application, that's basically a workflow. Now to do that, you basically have to define the script or trace file that you mentioned in your package store JSON file. So to do that, what you're going to do is go to your demo folder here, right click here and then let's say we create a new JavaScript file. Call it script or Chase and then we'll click OK now on the script. or JS file, let me enter the code that I have already coded and then I explain to you step by step what is happening now, so now let me zoom in a little bit so you can see, this is basically my script or trace file, so no Don't worry, I will explain each and every step to you and then you will clearly understand how we send information to the client and how the server sends us the response initially as I told you. before that, you know we had installed Express, so what we're going to do is first go import Express, so to do that, what you're going to do is mention Const and Express and then equal to a require Express which you're basically, you map it to Express available here and then you just import that particular library here.

The same goes for Joey, so both libraries are imported into your file. Now what you have to do is create an Express application directly to Do that, what you're going to do is basically use this particular variable that you created here that's basically expressed and then you're going to assign it to the application variable, so in addition, what what we're going to do is use this. application variable to understand the application and the distance actions in this application, so we are going to use this, so now when I say we are going to use this particular variable, you basically have to make sure that you know that that particular variable is the wearing.

Well, for that you're just going to put the use of application point and then you're going to mention Express or Jason because we want to use a JSON file, what I mean by JSON file now, for any application to work, you have to put in a database. you can use my sequel MongoDB or any other type of database, so now I'm going to connect it to any of those databases. I'll just use a JSON file that has a list of the data like that. enter and that will be stored on a server so the data is basically stored in JSON format that is the reason why we will use Express not Jason now we are talking about the server so when a client sends a request to the server initially the server has to be running then it needs a specific port so what I did was assign the port environment variable automatically to 8080 so basically what happens is you don't have to assign it again and again when you use an environment variable automatically.

What I did was you know that the server will be running on port 8080 and then just give a result that you know that yes the server is running or not. I just printed a log message that says they are listening or the port and then it will mention the port number, which will basically be eight here, so to make sure that you know that the server is running and then you know that the server is connected to our system which is basically our application where we want the data to come from, then We will simply use this command sing AB dot listening and basically we will create the list of servers on the port which is 8080 here and then we will show the message so that it is with the server now if you notice I have told you one thing here that it is a client will send the request to the server and the server already has a set of data so to basically define that data I have created a clients object so here that is basically the clients object which has a specific name which is basically a title and an id, so this particular data will be stored initially on a server and then we can play with the data based on any request we send, so what will return the data?

That is, give data to the server. After that, let's get started. you know, basically understanding the HTTP methods that I just discussed with you, that is, post and delete, so what I'm going to do in this lab is basically get all the data from the server and then. Basically I am going to find information about a specific customer, I can also delete information about a customer and finally I can also update information about a customer, so let's understand the same, initially let's start with the get method, if you remember from our presentation that the get method was basically read the resource so what I am going to do is mention any URL and then what I am going to do is if I just type a URL then automatically the message should be displayed correctly so here I have mentioned the URL which is going to be split or whatever localhost colon 8080 slash orthotic Lee, this will basically send the message that you know you're welcome to the ad breakers REST API now here if you sing what it is. the parameter so basically a request and a response are the parameters that are used in the get method, other than that when I say AB dot ket what I mean is that basically we want a controller to handle all the requests in a URL specific, now this.

The URL I have mentioned is as per my convenience the users complete perspective on which URL they want to mention, so you can mention the forward slash even then the code would work and even then you would show the result, so here the request is basically what it is and from the client side and the sponsor is basically what is sent from the server side, so the request here will be the URL, so whenever you type localhost colon 8080, the slash from the client side it will be sent to the server and whenever the server identifies this particular url this particular message will be shown in the next message which is AB dot ket and then we mention in the api url to the clients so now what what I'm going to do is basically I want the list of clients, so that's basically whatever list I mentioned in this particular object, so what I'm going to do is I'm going to similarly mention again the URL which is basically localhost colon 8080 /ki slash clients , so whenever a client types this particular URL, what I want in response is basically the list of clients that we had mentioned and that we had stored on the server side, so it's basically the five details, so for do that, what I'll do is not mention the rest command, send and mention customers here, so that's basically returning our customer object now let's say you know we want to get the information of a specific customer, let's say you know we want get Josh's ideal information right so basically their IDs so what I've done is in the URL I mentioned that you know it's going to be slash API slash customer slash ID so whenever you send the request from the client side, what you have to mention where you are basically on localhost colon 8080 /ki slash customer / - sowhenever you send this request a response will be sent from the server side which will show you the details about the second ID which is basically titled Josh and ID - B - so don't worry I will show you all the results when you run these codes.

So before that, let's understand these codes step by step. Now, if you're wondering how this happens, how does the REST API understand the fact that it knows we have to look up the ID? On the server side, that's basically what's happening. through this particular line here, so we basically assign the client object to the client point and then what we're doing is any query parameter that we're passing in the URL is basically checked against the client ID, so , for example, is a client ID. present only if successful will return data; otherwise, let's say you know there's no specific customer ID, for example, let's say you only have five IDs here right now, let's say you know if someone just types a slash six, so basically you're looking for the sixth ID and you know that there is no sixth ID present, so what happens is that it will show a four zero four error saying that it can't quite find what you're looking for, so basically this is also the user's perspective on how to do it. you want to display the data so i used four zeros for the error so that is basically the status i am checking the client is not found and then it shows this particular message so that is what happens when the client id is not present now.

I hope you know that you have understood the get method. Now let me run this code and show you the results. To show you the result and test the app what I did was use Postman so Postman is basically a chrome plugin which is used to send the request to the servers so I already installed it otherwise it's very simple to install, so what you can basically do is just click on the plus button here and then you can mention the URL. So as I was telling you, you have to mention the colon of the local host 8080 and let's say we mentioned the bar and then here you basically have to choose the method, so now I am choosing the get method. before you press send, what you have to do is start your server correctly, so what I'm going to do is go back to my command prompt and then I'm going to mention the dot chase node script, so once I mentioned you'll clearly see an output that you know is listening on port 8080, which It means our server is up and running now.

If I come back here and then if I click send, you'll see that you know we got a message on the screen. say welcome to the Eddie Rakers REST API, so that's basically what you saw here, so every time we mention a forward slash you will see the result as welcome to the Eddie Rakers REST API. Now let's say you know we mentioned slash API clients then according to our code we have to get the list of clients so I'm going to go back and then mention API slash clients and let the method get again and click submit, so once you click submit, you can clearly see a result that We know that we have correctly maintained the five details that we had mentioned in our J file script, so that's basically the list Of customers.

Apart from that, we also saw one more thing, you know, if you want to get information about a specific customer, so let's say. you know you want to get information about the third customer so that's basically ID three so I'm just going to put a forward slash here and mention three and click submit here so when you click submit you'll clearly see a result with that title. Tyler and ID three, this is how the get method basically works and that's how basic their API is to help you connect the request from the client to the server and so that the server can send the response to the client.

Now let's move on to the next method. that is the post method, so if you remember from your HTTP method you will see that here the post method was used to create correctly, so whenever you want to create a resource you use the post method, so now let's just create new data. Let's say you know we want to create new data and then we want to send it to our server, so what you're going to do is use the published application, so the application is the same variable that you created here. it's basically for our application variable, so app dot publish and then what you're going to do is mention API bar clients and then what you're going to do is just mention the title if the title is okay and if it is. validated basically when I say validate customer what I mean is that we have created a function to validate the information about the customer so only if the information is present in the correct format the customer information will be validated and yes , the customer information will be sent. on the server or if not, it will automatically throw an error, so here basically our function validates the Tila client information and our condition is basically that you know that the title must be a minimum of three characters, if it is less than that. so obviously it's going to see that you know it's not valid information and then it's going to show an error so that's basically what's happening so if I go back to my post method here you're going to see that you know if we're going to use this validate client function and then if it is validated what will happen is automatically the customer id will be increased by one and the title will be stored based on the title that you mentioned so basically that is what will happen here so remember the fact that from our Customer ID is automatically incremented.

You don't need to mention the customer id in your request, you just need to mention the title and then if the title is greater than three i.e. it has a minimum character value of three, then you move forward. and then automatically the data will be sent to the server, so when I say automatically send, it has to pop the stack properly, so initially our server had five values ​​in its stack, now we will not push the sixth one as well, so to that's what we do. What we're going to do is use this client function dot push client correctly, so basically we're going to send the new value of the client object to the client and then pop the stack once that's done, we're just going to send a response again.

I come back to the client saying here that particular id has been created on the stack, so let me do the same thing here. I'll go back to my postman and now let's see, I put the post here and then I'll come back. to API clients and then what I do is I go to the body here and then choose raw and let's say I copy this part and base it here and let's say we mention the name to mark correctly, so the mark basically has four values ​​of characters so that means this customer information needs to be validated so here I'm going to mention the title mark and then in the text option I'm just going to go and add Jason so basically this is going to be identified as a JSON object and then what I'm going to do is I'm going to click submit so once I click submit you're going to see a result that you know the automatically generated id is six which means we had five and then it automatically increments by one now if I go back to the obtaining. here and then I click submit, you see the information of the six values ​​that we have stored on our server, so basically a stack has increased, this is how you can use the post method and now you move forward with the port method. is basically used to update an existing resource so if the resource is not found it will again throw an error but yes if the resource is found it can definitely be updated so let's see the same how that happens so for update a resource, let's say you already know.

We considered an example of how to correctly update the ID name of a specific customer, so let's say you know we had all six correct IDs. So for example, let's say we update the ID of some customer 3 and then we mention that the name is Tyler Patterson, so stop that. What I've coded is basically that every time you dot put the application, which is basically an application, it comes back to the same object that you created here, which is the Express application, as long as it's with a put method and has a specific URL that be a client and then you mentioned the ID, what were the IDs that you want to update every time the client sends this particular request.

What happens is that initially it is discovered first whether the client exists or not, for example, let's see that no, we mention that the ID is 7 so that we know that unit. is not present on the stack so what happens is it will throw an error so here I put the error 4 0 4 and then I mentioned that the text is not found correctly so it basically says that the client is not there. found, so there is no resource with ID 7, so obviously no source can be updated that way, but yes, if the client is found, for example, we are taking a third party for the client to be found , Then what will happen? is that it will just validate the customer, so in your input let's say we will put "I will be partisan" and then every time you mention this title automatically the title will be updated for the third ID.

Now after everything is done the server has to send a response is also correct, that is what this particular command is used for which is the response from the end client so basically the client object is updated with the new ones values ​​and then the response is sent back to the client so let's look at the same thing so what I will do is I will take the third one and then I will mention the title to beat Tyler Partisan and then I will choose the message to be placed here and then I will click on submit once I click submit if I scroll down.

You'll see the result that you know the title is Tyler Patterson for ID three right now, so now if you just want to look at the stack, what I'm going to do is delete this ID here, click submit here. again and then you will see the updated list that you know that ID three has been updated and the new value is Tyler Patterson, that's how you can basically use the put method to update your resources and now you finally get to the final resource guys. than the parent resource, so the deletion method is basically deleting any specific resource, so it's as simple as the name suggests.

To do that, what I did was choose this Abdur removal and then choose that URL to be API. Client ID, so what I'm going to do is sniff for a specific ID, let's say the second ID. I want the data for the second ID to be removed, so that's what I'll send in the request and then. What will happen is that initially again a condition will be checked whether you know the client exists or not, for example I would say the id does not exist and then automatically again an arrow will be sent saying you know it does not exist. found, but Yes, if the client exists and what happens is that you basically have to delete that particular data, so you basically join from that particular data, all the data that is present in id2 is deleted and automatically the stack advances right at the beginning, now you had six values. you only have five correct values, but yes, remember the fact that you know the ID is not automatically updated here, the ID remains the same.

I'll leave it to you to explore how you can update the ID automatically whenever your resources are deleted. from the server so apart from that finally after the data is removed we want the server to send a response to the client so again we use rest or send to the client which is basically our object. Now I'm going to go back to my postman and then I'm going to choose this delete option and let's say you know I mentioned the ID in b2 and then I'm going to click submit, so once I click submit you'll see a result that you know, the title George and ID.

Two will be deleted, so when you come back to the method, put the customers here and delete the id, you will see that we get the data for one, three, four, five, six, but the second one is missing, that's because you know the data was deleted . That's how basically, guys, you can use various HTTP methods, which are basically the REST API methods to communicate with the client and the server and understand how the server processes a request from the client and how the server sends it back to the sports. With this we come to the end of the session.

I hope all of you found it informative, so if you have any more questions related to the session, please comment in the comments section below until then. That's all from our site today. Thanks and happy learning. Wait. You have enjoyed listening to this video, kindly give it a like and you can comment any of your doubts and queries and we will answer them as soon as possible. Find more videos in our playlist and subscribe to Edureka channel for more happy learning.