ActiveModel::Serializers VS Grape

Hey folks, I've been using FastJsonapi::ObjectSerializer in past projects, but it is now deprecated and it's successor is "in maintenance mode! ". The og serializer had no release since 2015.

Further reading: Active Model Serializers Github

In order to use our serializers, first we must install the gem into our gem file. we can do that by first grabbing our "Active Model Serializers" gem file from "https://rubygems.org/gems/active_model_serializers/versions/0.10.13". We will copy the gem from this website and paste it into our gem file in our application like so

Today I thought I'd run through a few of the powerful things that the ActiveModel::Serializer gem brings to the table when used in a Ruby on Rails application. Sure, there are faster alternatives, but AMS is the first one I learned how to use, and thus it holds a special place in my heart. Quick question before we dive too much deeper, though...

AMS

ActiveModelSerializers to build JSON views

Might be overkill for your situation but I generally use https://github.com/rails-api/active_model_serializers for my projects. Otherwise just build the hash you are sending back to the frontend with standard code.

On the other hand, we have Active Model Serializers. This gem is also deprecated but has another stable version 0.10. I also found Blueprinter gem. I've never used it before and don't know its limitations.

Grape’s support extends to standard conventions, multiple format support, content negotiation, versioning, etc. The complete guide to Grape to develop REST-APIs, test the API and analyze the performance metrics is available on its official GitHub page.

Grape (ruby-grape.org)

I'm very ambivalent about Grape, but this very much reminds me of something I do really like about it: the param validation. https://github.com/ruby-grape/grape#parameters

I am currently working on developing and api using grape and devise jwt for user user authentication.

Your RN app will be making http requests to your server, so it doesn't really matter what backend language/framework you use. If your React work was also utilizing http requests to fetch data, then there shouldn't be much of a difference. If your backend is a simple JSON api, checkout Grape. You can tack it on to any existing Rails app.

I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)

Grape is a REST-like microframework written in Ruby programming language. Grape is also considered among the best ruby frameworks and can be used to run on top of Rack or can be used to complement the existing web application frameworks such as Sinatra or Rails. The latter can be done through the DSL-based REST-API for communication. The Grape ruby web framework facilitates efficient and meaningful APIs working in the web application domain.

Take a look at Grape - https://github.com/ruby-grape/grape

I love the Grape gem for building APIs - might be worth considering if you are building something new: https://github.com/ruby-grape/grape

Grape is a REST-like API framework for Ruby. It’s designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. 9,200 stars by now