Right now we generate one schema for the entity and Infinispan value. And another schema for the Infinispan key which contains the entity id

// peuso protobuf message
message Cloud_id {
    String id required = 1
}
message Cloud {
    String id required = 1
    String name required = 2
}

In the simple cases where the id is not a composite id, we could simplify things by just sending a native String instead of a Cloud_id message. It would probably be a more natural mapping that a user would use.

Let's discuss that as a simplifying option.