Cfrtjryk

I have a problem which approach is best. Please imagine system written in a hexagonal architecture where each service method accepts class or classes. Let say for example my method create User.
1. Approach:
Of course, it is the only example and real classes can be more complex to accept more arguments etc.
I have a class like this:

class CreateUserCommand {



    private final String name;

    private final String username;

    // let say 10 other fields emails etc it doesnt matter





    private CreateUserCommand(String name, String username) {

        this.name = name;

        this.username = username;

    }



    public static CreateUserCommand createFromApi(CreateUserRequestApi createUserRequestApi) {

        return new CreateUserCommand(createUserRequestApi.getName(), createUserRequestApi.getUsername());

    }



    public static CreateUserCommand createFromRabbit(CreateUserRabbitMessage createUserRabbitMessage) {

        return new CreateUserCommand(createUserRabbitMessage.getName(), createUserRabbitMessage.getUsername());

    }



}

2. Approach:

interface CreateUserCommand {

public String getName();

public String getUsername();

//other 10 methods like getters

}

And for each entry point to my system (api, rabbitmq etc) I will create adapters for this interface so in my service I will operate on the interface instead of real implementation of a class as I do in the first example. What approach do you thinks is better and why?