These videos and explanations are absolutely unbelievable. No matter what is being discussed. There is a clarity and absolutely brilliant explanation. I have worked in universities and seen the best but this goes beyond the best. Just incredible.
I am studying in Concordia university,Canada on web services...Ur tutorial on web services is much better than the one taught in Canadina universities buddy..Great job..
Absolutely blown away by your educational content, Raghav! 🚀 Clear explanations, well-chosen examples - making learning a breeze. Your work is expanding my knowledge. Keep the outstanding content coming! 🌟💻📚
i like your explanation bro. Nice job. You also provide how the process of web service and much better than the one taught me (make me more confuse i think haha..) But i appreciate if you can slow down while speaking. some word i can't catch up...maybe about pronunciation issue...
Very good illustration Raghav!, I just started to learn about web services. I have a quick question ( might sound silly!), as in SOAP medium is HTPP ( post) for request then what will be for response? I am assuming no GET is there like REST?
Hello sir, last month I attended interview. But they told me to learn web forms web services and and SQL server reporting service(SSRs). So I joined one company, but here they are teaching me vb.net. so I am referring RU-vid videos. So is it really helpful. To get knowledge about web services The 7 videos you have uploaded on web services is enough or not.
Hi Padma, glad to know it helped. 7 videos are good to get a very good foundation and with this knowledge you can explore more. There is a lot to learn
Hi Mohit, The major diff is SOAP is governed by a strict protocol while REST is much flexible. Usually companies now are moving towards REST as its is flexible, easy and fast.
Hi Raghav,Very informative videos, keep up the good work. I have learned a lot watching your easy to follow tutorials. Quick question, in what way is this web services architecture so different from your traditional web server serving up requests that a client makes to get data? My browser, when requesting a web page from a URL pretty much does the same thing, that is, sends an HTTP request, and the web server responds with something. What is so unique about web services as opposed to this?ThanksRaj
Hi Raj, so you have a web application and a server. The application sends a requests and the server services this request and sends back the response. This is all good as long as the client and the server can understand each other. But what if your application(client) needs to get response from another server (3rd party) that does not understands the format / protocol of your request. Or your application needs to interact with another (3rd party) app. This is where Web Services come into picture (at a high level)
By the service provider are we talking about BT for example sorry if that sounds dumb im thinking of it as like a web service is something like DNS implemented by your ISP is SOAP the same as this??
@@RaghavPal Thank you for clarifying that. Yes, my desktop applications must be able to talk over the internet. Basically, data must be exchanged between them via sockets. Another question I have is, if heavy weight data (e.g., a million floating point numbers) must be passed between the two applications, can REST be used? I guess REST is only a specification, so, maybe I should use grpc or something that is based on REST?
I have a doubt, in that make my trip example, who is client: the browser on which make my trip app is running or make my trip app?or there are two clients, one the browser communicating with make my trip server or app and second is make my trip app itself that communicates with airlines' server?
In a basic client-server concept it is whoever is requesting is the client and who serves the request is a server. In general here 2 applications are interacting with each other, make my trip sends request and flight applications serves the request.
Hi Kartik, I will plan a detailed session, This one explains well - medium.com/@programmerasi/difference-between-api-and-web-service-73c873573c9d#:~:text=The%20only%20difference%20is%20that,can%20communicate%20with%20each%20other.&text=Web%20service%20also%20uses%20SOAP,as%20a%20means%20of%20communication.
An API (Application Programming Interface) is the means by which third parties can write code that interfaces with other code. A Web Service is a type of API, one that almost always operates over HTTP (though some, like SOAP, REST can use alternate transports, like SMTP) 1. All Web services are APIs but all APIs are not Web services. 2. Web services might not perform all the operations that an API would perform. 3. A Web service uses only three styles of use: SOAP, REST and XML-RPC for communication whereas API may use any style for communication. 4. A Web service always needs a network for its operation whereas an API doesn’t need a network for its operation
