Skip to content

Service Fabric and Communication subcategories #3

@chheis

Description

@chheis

Migrated from PLeVasseur/eclipse-sdv-projects-landscape2#20
Original author: @budrus
Original URL: PLeVasseur/eclipse-sdv-projects-landscape2#20

I'm struggling a bit with your current subcategories in Service Fabric and Communication
I did not create a pull request as there is a) unfortunately no clear definition or the boundaries are blurry and b) I cannot speak for others.

My point is that iceoryx, for me, is a shared memory communication technology, which is for sure within the middleware domain but not a communication protocol which is typically associated with an on-wire format to communicate over a network. Zenoh is for me much more of a protocol than iceoryx and Zenoh is in the Middleware and Frameworks subcategory. We could introduce 'Data Plane' as the subcategory for iceoryx but this would mean introducing even more subcategories and maybe further discussions.

My suggestion would be to merge Middleware and Frameworks and Communication Protocols in a category Communication Middleware and Protocols. I'm also struggling with Eclipse Heimlig though

What are your thoughts?

@PLeVasseur @chheis

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions