What is the best way to make a REST API in conjunction with 1s 8.2?

Question

1C

Good afternoon! First encountered.
There is a base in 1s 8.2. It is necessary to make a REST API for integration with other services (Internet stores, etc.). I plan to do this:
1. Use RabbitMQ to transport data between 1s and the rest of the service.
2. To exchange with rabbitmq and 1c, create an external component.
3. To implement the REST API itself, use Yii2.
Now what the REST API should do:
1. Authorization (this is already clear).
2. Receiving data and processing accordingly i.e. if the data needs to be sent to 1s then transfer everything to rabbitmq.
2. Data transfer at the request of customers.
Make the client part in AngularJS and make all sorts of csv xml pdf on the client.
How correct and reliable (correct, convenient, or are there other easier ways) to implement?

Answer 1

What is your task? Do you need stability or just want to learn new technologies?
If you just need to connect the 1C database and the online store, then you need to do this using either the experience of exchanging with Bitrix in typical trading configurations, or connecting 1C to the site API, or connecting the site to API 1C. The more entities you introduce into the architecture of the future solution, the more "thin" places you will have and the more dependence on heterogeneous technologies:

1. the need to read a large number of manuals or attract additional specialists,
   
2. the requirement to monitor news across all technologies in search of messages about critical vulnerabilities and errors,
   
3. the need to deal with both the mono-errors of technologies and the unpredictable results of their synergy, followed by long googling and scouring sites / forums where you will be spoken to in terminology that sounds the same, but adherents from different IT fields put different meanings into it (a classic example in 1C - the term "thin client")
   

.

Answer 2

What's wrong with SOAP WebService?