ServerPipe: Marketplace and aggregator for back-end software services. Need validation and tips.
Hey hackers. I was thinking about building a marketplace named 'ServerPipe' where back-end developers could build and sell micro services through apis.
ServerPipe, will be a marketplace and aggregator for back-end software services.
As an aggregator I plan standardize the back-end api documentation and give the developers tools in order build their services.
Do you think it a good idea?
What would you like to see from this kind of service?
Any more tips?
Seems like www.onegraph.com
Tanks for the feedback.
I will check onegraph out.
great idea! is it for public APIs only?
would make sense to standardize the actual API interfaces into a single interface in a particular niche... for example there are multiple services that provide financial data (google, yahoo, etc) and all of them have their own APIs. So your product would unify (aggregate) them into a single API interface, i.e. a wrapper around all their interfaces to just provide a single endpoint that would re-route calls behind the scenes.
Thank you very much for the response.
No, it's for all(!) APIs in my marketplace, there will only be one endpoint and one call for example:
axios.requestType(
{
url:'/ServerPipe/usedApiEndpoint',
headers: {
AppName: 'myApp',
Authorization: 'AuthToken',
ResponseAs: 'JSON (for MBaaS support if any)',
...
}})
I would definitely check it out but it sounds like a big project. I like the idea of standardizing the documentation. Might be good to also standardize some common usage and API formats. That could be overreaching though.
First of all thank you very much for the response.
Standardizing the third-party API is a BIG challenge.
Of course, the ambition is to "twist the developers arms" in such a way that the API will be as similar as possible to all service providers.
You could have an entirely graphql section... Might solve that problem for you at least partially.
I'm not very familiar with that technology, can you give me an example of what you mean?
GraphQL (https://graphql.org/) is kind of an alternative to REST that allows you to pick and choose what you get from your data model/backend with a JSON-like query language. It makes it a bit easier on your front end developers because they don't need to have a new endpoint to get the data they need, and there's less of a chance of over-pulling stuff you don't need to get what you do need.
There are cons but that's the general idea. I think it was made by FB but also could be wrong.
Thanks for the feedback I will of course look into this issue in depth.