1. RESTful Web services Interview Questions and Answers
For the interview perspectives, there are so many questions and answers in Java. using Although there can be so many questions raised in the mind of the interviewer when specially web services requirement they have. I tried to add some of the most commonly interview questions which my friends and I encountered the interview. This section consist only RESTful web services interview and you can find another page of SOAP based web services Interview questions and answers.
Q1. What is REST Web Services?
REST is the acronym for REpresentational State Transfer. REST is an architectural style for developing applications that can be accessed over the network. REST architectural style was brought by Roy Fielding in his doctoral thesis in 2000.
REST is a stateless client-server architecture where web services are resources and can be identified by their URIs. Client applications can use HTTP GET/POST methods to invoke Restful web services. REST doesn’t specify any specific protocol to use, but in almost all cases it’s used over HTTP/HTTPS. When compared to SOAP web services, these are lightweight and doesn’t follow any standard. We can use XML, JSON, text or any other type of data for request and response.
Q2. What is a Resource in Restful web services?
Resource is the fundamental concept of Restful architecture. A resource is an object with a type, relationship with other resources and methods that operate on it. Resources are identified with their URI, HTTP methods they support and request/response data type and format of data.
Q3. What are advantages of REST web services?
Everything in the work has some advantages and disadvantages but in the software world when you choose any, you must see, what you required at that point in time.
Some of the advantages of REST web services are:
- RESTful web services carrying forward more than 40 years mature http web world.
- Learning curve is easy , as it works on HTTP protocol
- Supports multiple technologies for data transfer such as json, xml, text, image, any formate.
- No contract defined between server and client, so loosely coupled implementation. But somewhere we need to maintain the contract of api between producer and consumer.
- REST is a lightweight protocol, why lightweight because of many aspect.
- REST methods can be tested easily over browser/ google advance client / postman etc.
Q4. What are disadvantages of REST web services?
Every thing in the work has some advantage and disadvantages but in the software world when you choose any , you must see , what you required on that point of time.
Some of the disadvantages of REST web services are:
- Since there is no contract defined between service and client, it has to be communicated through other means such as documentation or emails.
- Since it works on HTTP, there can’t be asynchronous calls.
- Sessions can’t be maintained.