ROS vs VSome/ip

edit

As-is, I believe the way you pose your question here is too open. Without extensive experience with both frameworks, there isn't much that can be said here.

I've found that in cases like this (determining whether one piece of software is 'better' than another), it's best to come up with some concrete user-stories, requirements and constraints.

Once you have those, you can start comparing the support for those in (both) candidates.

And even then this will most likely be a rather superficial comparison, as someone with (a bit of) experience will most likely be able to achieve 'anything' with 'anything' (ie: good cooks are often better than mediocre ones, regardless of the ingredients they work with).

Thanks for your answer, by my Question I am mainly questioning the Design concepts behind both, I am not experienced with neither of them, But I managed to do some simple projects with both and I can find that - from this simple projects POV - they have alot in common

• both have a serves oriented Architecture
• both use the publish/subscribe design pattern
• both can define a new data type to be the transfer unit (ROS->topic) (vsomeip->define new data type)
• both depend on underneath IPC protocol to get the job done
• both can nodes or services can be either on local network (using loopback) or on different machines

please excuse my narrow knowledge in both. this question is not for a specific project, rather for analogy and learning.

thanks

i am looking for combining both the concepts to achieve communication between those architectures. Please share me some information about how can i achieve this interface between ros and vsomeip.