Currently, the only callback exposed by sumo_backend is start_link, and that function receives a list of options, which can be handled by sumo_store:init/1 as well, so there is no need to keep two separated behaviours, the proposal would be create a single one called sumo_repo.
Currently, the only callback exposed by
sumo_backendisstart_link, and that function receives a list of options, which can be handled bysumo_store:init/1as well, so there is no need to keep two separated behaviours, the proposal would be create a single one calledsumo_repo.