How to combine multiple systems into a single API?

Question

SharePoint

Hello!
I am a novice .NET developer, I am faced with the problem of integrating several systems (sharepoint, project, 1c, databases) to implement a centralized aggregated API to work with them.
I found articles on the net about the Gateway API pattern, which is based on the idea of ​​microservices. I liked the idea, however, I can not find clear examples of the implementation of such APIs.
Colleagues, please share your experience on how to approach this problem.

Answer 1

Nope. Your task is not worth it.
Your task is to solve some specific business problem of transferring specific data from sharepoint to 1C, for example.
Start from this. from specific requirements. That is necessary - those calls also do
And to your statement is to drag not clearly what API. 100% of all 1C functionality or what?

Answer 2

What is there to think? You take and make your own service that implements all the necessary requests - namely, it redirects to another service and, if necessary, formats the response in the right way.

Answer 3

Here the task is extended and not particularly trivial, here it is better to proceed from whether it should work on the ground or in the cloud? If on the ground, which is obvious, then I would look towards my main service or service receiver + esb in the face of the MS Message bus, which acts as a bus to systems and behind it a series of interfaces that already carry out serialization and CRUD model. About the bus, it is well described here: https://m.habrahabr.ru/post/254059/
As for SharePoint, it is better to lick CSOM and its asynchronous advantages.
Why is it better, firstly, it is more like an ecosystem with fault tolerance and a simpler approach to updating and further development, but in the beginning you will have to work hard and set up an envelope of services and esb. In the future, you can just as easily connect more additional integrations just outside the home interface, notation and scheme, and go live.