Carlos Andres Bolaños R.A.

`shards_registry` will be a very good example of using `shards` and at the same time a very useful lib too, since there will the analogous [Elixir Registry](https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/registry.ex) but in Erlang.

This is a **Nice-To-Have** issue, since it might be very complex/tricky.

There are some callbacks that might be optional, maybe `find_by`, `create_schema`, etc. For those functions, we should identify them and treat them as such. For example, it would be nice...

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...

Currently, when is needed to execute a query with sort params using `find_by`, you are forced to pass the pagination parameters as well. The proposal is to implement `find_by/3`: ```erlang...

The idea is to implement a rebar3 plugin `rebar3_sumo_plugin` (check the doc [HERE](https://www.rebar3.org/docs/using-available-plugins)) in order to automate some task, for example, the model generation, at least a good skeleton that...