Is the rest api sufficient for the needs of internal services?

Question

API

The question is for those who participated in live large projects with a well-thought-out rest api. Did you need it for internal needs? Was it comfortable? Or maybe for some other reason you preferred to work with storage, etc. bypassing the API?

Answer 1

rest api is more convenient:
- api hides implementation details. The storage can be replaced by another, more productive one, the architecture of the application can change a lot bit by bit
- as a result, individual parts of the application can be written using completely different technologies depending on performance requirements, for example. Bottlenecks can be implemented in go/c++ etc.
If parts of the application communicate extremely intensively with each other, binary protocols will be more efficient due to higher throughput and lower overhead (marshalization instead of serialization to text formats).
Again, bottlenecks can be asked to communicate through binary protocols (message queues, for example, caches, etc.) and something through the rest. strongly depends on the task and on the goals pursued by the developers.