This issue will migrate BOPTEST-Service to be used as the only deployment architecture and RESTful API. The primary advantage and reason for this is to alleviate the need to maintain the two closely matched but not exact RESTful APIs, alleviate developers and users having to develop and maintain interfaces for each of them, and generally streamline the implementation of new BOPTEST features which are also supported by BOPTEST-Service. A downside is that the service architecture is more complex for those who use BOPTEST locally. However, with continued usage of docker-compose, users will still be able to deploy BOPTEST easily and in the same basic way.
This issue will migrate BOPTEST-Service to be used as the only deployment architecture and RESTful API. The primary advantage and reason for this is to alleviate the need to maintain the two closely matched but not exact RESTful APIs, alleviate developers and users having to develop and maintain interfaces for each of them, and generally streamline the implementation of new BOPTEST features which are also supported by BOPTEST-Service. A downside is that the service architecture is more complex for those who use BOPTEST locally. However, with continued usage of docker-compose, users will still be able to deploy BOPTEST easily and in the same basic way.
Todos: