Communication between two or more applications is often everyday stuff, and it might seem that there is not too much to add there as this subject has been covered pretty well in the last years. Thanks to that, multiple patterns and standards have emerged. You no longer need to think about how the response format should look like for your REST API (go with JSONAPI and stick to the conventions) or figure out the authentication/authorization protocol (go with OAuth and the security headaches won’t bother you).

However, things like format or authentication are most often the concerns that you need to solve if your API is exposed publicly. What if you don’t need a publicly available API, but merely something that will be available for your own (micro)services and nothing beyond that single ecosystem? In such a case, you might go with a bit less popular, yet a more suitable approach - RPC with RabbitMQ.

Read more