Draper VS Kaminari

So what about the world outside Rails defaults? There are quite a few independent projects trying to help build components in the Rails view layer, among the more famous being Draper (utilizing the decorators pattern) or Cells (full-featured components in views). In the end, we decided to take a deeper look into a relatively new one – the ViewComponent framework.

If you are not a big fan of writing Rails custom helpers, you can always opt-in for a View Model pattern with the Draper gem. Or you can roll your own View Model pattern here, it shouldn't be that complicated. If you are just starting out with your web app, I suggest starting slowly by writing custom helpers and if that brings pain, turn to other solutions.

The Draper gem is the one I'm familiar with which does this well, I'm sure there are others.

Don't introduce decorators and view models. Use helpers instead. Don't extract domain models. Put the code in the ActiveRecord models and the controllers. Don't reach for interactors to model your domain logic. Don't try to avoid duplication too early.

7. DRAPER

With around 50 new gems released daily, it is common to use trending libraries for managing everyday tasks. You probably use Devise for authentication, Cancan for authorization, Kaminari for pagination, or run tests with Rspec.

I used kaminari for paginating.

Note that this example uses methods from Kaminari, but you can adapt it to any other pagination method.

- Pagination system with the Kaminari gem (https://github.com/kaminari/kaminari)

3- To use pagination we will be using the kaminari gem. Simply add this line to your Gemfile.rb and hit bundle install

There are many Ruby Gems like Kaminari for pagination that works with Postgresql/ActiveRecord but not DynamoDB

Kaminari

2. KAMINARI