How to use vsomeip repository in context with CommonAPI?

[nachtfuchs]

As the discussion in #535 highlighted, CommonAPI is an abstraction for Inter-Process Communication. So I ask myself how to smartly use SOME/IP with CommonAPI? Can anybody share the "ideal model" how to use the CommonAPI and vsomeip to implement dozens of services?

Background: I want to use SOME/IP to run it in a Hardware-in-the-Loop environment. In my bottom-up approach where I come from CAN and FlexRay busses, I started to implement SOME/IP. I am having only this narrowed view right now. Recently, I noticed that I cannot manage this myself, so I searched for a C++ library and found "vsomeip". I manage to make progress in implementing the vsomeip library. Still with this tunnel view that the vsomeip library is going to manage the communication. It is a rocky road. Now, I start to notice with more attention the existence of CommonAPI, and ask myself whether I am missing a bigger idea. Is CommonAPI the actual way to go "to use SOME/IP"? Does it make my users life easier?