Blueprinter VS jsonapi-serializer

Blueprinter is something we use on a project, it's also having difficulty staying alive, but right now there is active development here, a fork from the original blueprinted gem.

Beware of this

Serializer: procore/blueprinter: Simple, Fast, and Declarative Serialization Library for Ruby

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

Blueprint

Just an FYI: While I agree that the blueprinter gem is awesome, there are currently no active maintainers: https://github.com/procore/blueprinter/issues/288

In a happy coincidence, we're knee-deep in the middle of a migration of our serialisers to use Blueprinter instead of AMS. One benefit, in this case, is that it lets you explicitly set what generator you're using, like so:

What made me think about this is that I'm using (maybe in the wrong way) some gems like Blueprinter and Amoeba.

I've been using Blueprinter so far, and it has been working great, but I'd like to ditch it if I can.

We use it extensively for one project. The only annoying bit involves defining the response json-schema. Luckily we are using a gem called blueprinter for JSON serialization, so we added a bunch of overrides that store metadata, so we can generate the json-schema with meta programming. You might need to find a library that would help you write the schemas fluently [1] / [2] to make it easier to define them.

Hi guys, I know that Hotwire is the sh*t in rails nowadays, but if you were to build an API with rails, which serializer would you use ? I have my eyes on jsonapi-serializer with oj , but I am not sure if that is the best option nowadays. The jsonapi-serializer repo is a bit confusing, regarding which version should I use, same for ActiveModelSerializer to be honest.

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.

There is a to_json method and recent benchmarks I found are placing a few ms above fast_jsonapi (which is no longer maintained) and slightly faster that jsonapi-serializer (which is supposed to replace fast_jsonapi according to their website).

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

Yeah at a previous company we started with grape, wound up hating it and just moved over to using the fast json serializer for our API endpoints instead

I might have spent a little too much time refactoring my code instead of building on features for my application, but my code is much cleaner and works very well to boot. The real test will be when I have copious amounts of records in my database and how long it takes to load it all on this single fetch request. I’m also attempting to learn how to define related links in the Serializer that JSONAPI says would be helpful in gathering data in later requests. I will attempt it and see how well it turns out. Until next time!

I miss https://github.com/jsonapi-serializer/jsonapi-serializer in the comparison, at the time the Netflix library was the fastest, don't know if this is still true.

- https://github.com/jsonapi-serializer/jsonapi-serializer