Testing if a web service API is RESTful [closed] - web-services

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
One of the technical requirements of the software I am working on is to provide a REST web service API.
As a consequence, I am now asked to create a manual or automated test checking if the software provides a REST web service API.
My initial thought is that this is not possible, as REST is not formally defined and is not a protocol. Some might even say that my API is not RESTful.
Is there any way for me to provide such a test?

Given that, as you said, REST is not formally defined, I think you'd need to go to the requirements writer and ask them what satisfies their criteria for being RESTful.

Related

Better User authentication?(aws cognito or Oauth2 or okta) [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
We have a requirement for a project and we are planning to use the User management and authentication service of 'Oauth2'.
Our application will be on AWS so we also wanted to check with AWS Cognito.
Could anyone help us decide, which is the better option to go with?
I would proceed as follows:
Build apps in a standards based / portable manner, via certified open source libraries
Start with Cognito and see if it meets your requirements / identify it's limitations. Avoid vendor specific libraries unless there is a good reason.
If you need to switch vendors you will be able to do so quite easily, since your apps will not be locked into AWS
Out of interest I built all of the samples on my Quick Start Page using Cognito. It is a good place to start because it is stable and low cost.
As a rule of thumb, no vendor solution works perfectly - there will always be gaps between what you want and what they provide.

API management/proxy: worth it for UI-consumed API calls/internal API calls? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Are products like Wso2/Apigee and other "api management"/api proxy tools worth using (and do people actually use them) in the following two cases:
API calls that are exclusively called by the UI of web-app
API's consumed by small numbers of systems inside a company i.e. no external users
I know the general use case of these tools is for managing external developers access to API's designed to share data/functionality with the outside.
While some features of api management tools might be irrelevant in the case of UI-called API calls and internal API calls, i am wondering if there may be a value to using them to gather metrics on calls made from the UI or internal users/apps.
Wondering if anyone actually uses api management tools for these purposes.

What advantages are there having a web site per web service versus per application in IIS? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
What advantages are there having a web site per web service versus an application per webservice in IIS7?
As far as I can see there is no advantage apart from being able to stop/start a single service when it is a website. It doesn't look like this is achievable with applications.
Web sites can have different bindings and host headers. With applications -- you can still stop/start single services via their Application Pools. You can also take advantage of configuration inheritance if you use applications.

How to write a web server (service) in OCaml? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 11 months ago.
Improve this question
I wish to write a web service server (using http protocol) in OCaml.
For a simple example, I want to write a http server. User can access it and provide parameter like http://myservice.com?i=1&j=2. Then my server get the request and parameters and calculate i+j and return the result.
Of course, my service will be more complicated for the calculation part. Instead of this simple example of calculation, what I really need to do is to
access the database (MongoDB) to get some data
access another 3rd party web service to get more data
calculate all data to get a result and return to the user.
So, I also need to consider parallelism / multi-threading, although I want to start with simple case first.
My questions are:
Which library should I use to first set up such a http server? I have looked into Ocamlnet 3 and think it might be a good candidate, but it lacks good tutorial and I still don't know how to use nethttpd or netplex etc.
How should I design the architecture of my web application? I know OCaml is not good at parallelism, then how can I make each service instance not blocking?

Executing an external Java Program from Siebel [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How can I trigger an external Java Program from Siebel? The Java program was custom written, when it is triggered it does some transformation on data. I would like to execute the Java program from within Siebel, is there a way to do that with Workflows or Business Service ?
Another way of implementing the solution is to bring the program into Siebel and call it as a Java Business Service. This methodology only works, if you have access to the source code and can invoke it. For more information on the methodology, a primer from the same author can be found here
http://www.impossiblesiebel.com/2010/04/java-business-service-jbs-tutorial.html
Expose Java program as a web service then create outbound web service in Seibel to call it, this tutorial explains how http://siebelunleashed.com/siebel-outbound-webservice-tutorial/