Currently the various services reply to different service urls, eg /api/hello, api/namaste, ...
I think it would make more sense to have a unified URL like, api/greet. This way it is not encoded into the URL what's supposed to happen. The task of the service is to "greet" and it does so in multiple languages, depending on the service targeted.
Also, in all cases the root route should be valid as well. Either have some content there with a link to the actual service url or it could also be a re-direct to the service URL. I guess it depends a bit where we want to go with this.
rafabene
commented
8 years ago
Currently the various services reply to different service urls, eg /api/hello, api/namaste, ...
I think it would make more sense to have a unified URL like, api/greet. This way it is not encoded into the URL what's supposed to happen. The task of the service is to "greet" and it does so in multiple languages, depending on the service targeted.
Also, in all cases the root route should be valid as well. Either have some content there with a link to the actual service url or it could also be a re-direct to the service URL. I guess it depends a bit where we want to go with this.