Use rest-assured as a general-purpose http client

Question

Is there any reason to avoid using rest-assured in an environment without testing? The syntax that the library offers for creating and processing requests is so compact that it seems that spending it on use only for testing. What question is asked, why is it intended only as a testing tool?

Answer 1

I am the founder of REST Assured, and he has always been focused on testing. For example, the default port is 8080, it comes with Hamcrest controllers (which is also used internally, so it cannot be excluded), and performance can probably be optimized somewhat. It also depends on Groovy, which can be a pretty big dependency to add to a production system if all you need is an HTTP client.

People, including myself, sometimes use it in production, because it is easy and flexible to use. Not all use cases require modern performance with a minimum of dependencies. Therefore, for certain limited contexts, REST Assured will probably make a lot of sense.

One of my goals with REST Assured is to retrieve a lighter kernel and eliminate the need to use Hamcrest and potentially even Groovy in the future. Some steps have already been taken in this direction when JsonPath and XmlPath were extracted into their own projects.