hello everybody! I'm a long time lurker but decided to finally properly join the community.
We have a standardised interface which provides various services for internal purposes and are thinking about opening them up so they can be utilised by others.
So, we'd provide a standardised interface & API which you call to use a given service. Random examples might include:
This are just examples to illustrate the concept. The idea is that there are tools which obviously exist elsewhere but what we have is a standard method of querying the service provider, unified response methodology & format and also new services can be added pretty quickly so overall it speeds up development work and reduces number of external services that are used.
You can think about it as a toolbox.
The ultimate question is - will you be interested in using proposition like this?
What services would be useful to you and sort of "I'm signing up if it's there!"?
What are other providers who provide something similar?
I like the idea. I don't think there is any developer here or anywhere worldwide who would not want to use your service if it fits their needs. Having that toolbox is very good. Of course I would want to use it. However your examples you gave about the services you provide , I do not need any of them.
So Yes we would use a standalone api or web service but only if it will solve our problem
thank Ben for your feedback. These are just examples to illustrate the proposition. Is there any sample problem you could think of that would be useful to you (even if already provided by somebody else or done internally)? Just trying to understand the type and caliber of a service someone might want use.
1 and 2 works for me