RESTful is just a specification, not a standard that forces you to use it. Following it can make your API interface more standardized and professional. Of course, you can also choose not to use it. Just implement it according to the specifications agreed by your own project team. RESTful mode: http(s)://server.com/app-name/{version}/{domain}/{rest-convention} Here, {version} represents the version information of the api. {domain} is an area that you can use to define any technical (for example: security - allow specified users to access this area.) or business reasons. (For example: the same functions are under the same prefix.) {rest-convention} represents the agreed set of REST interfaces in this domain.
There are a lot of RESTful guarantee specifications available online, so I’ll just post the address here for your reference. http://www.coderli.com/transl...
RESTful is just a specification, not a standard that forces you to use it. Following it can make your API interface more standardized and professional. Of course, you can also choose not to use it. Just implement it according to the specifications agreed by your own project team.
RESTful mode:
http(s)://server.com/app-name/{version}/{domain}/{rest-convention}
Here, {version} represents the version information of the api. {domain} is an area that you can use to define any technical (for example: security - allow specified users to access this area.) or business reasons. (For example: the same functions are under the same prefix.)
{rest-convention} represents the agreed set of REST interfaces in this domain.
There are a lot of RESTful guarantee specifications available online, so I’ll just post the address here for your reference.
http://www.coderli.com/transl...