SQLite3 VS Blueprinter

Extralite is a gem for working with SQLite databases. It is blazing fast (up to 11x the performance of the sqlite3 gem), and provides a rich API for accessing database data in a variety of formats.

DB: sparklemotion/sqlite3-ruby: Ruby bindings for the SQLite3 embedded database

# This configure_connection is run when each new connection is created. # see https://github.com/rails/rails/blob/main/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb#L1112 def configure_connection super puts "Configuring DB connection with app-specific PRAGMA statements" conn = self.raw_connection # see https://github.com/sparklemotion/sqlite3-ruby/blob/master/lib/sqlite3/pragmas.rb conn.synchronous = 1 # normal # this is a permanent pragma but in case DB is brand new, no harm is invoking it conn.journal_mode = 'wal' # this is unnecssary b/c rails' sqlite3adapter turns it on by default conn.foreign_keys = true # this is not yet supported with convenience method #conn.analysis_limit = 400 # PRAGMA temp_store = 'memory' # hold temporary indices and tables in memory # conn.temp_store = 2 end

That looks like you're missing the ruby module, not the OS package. If you're using bundler to manage your dependencies, add gem 'sqlite3', '~> 1.3', '>= 1.3.11' to your Gemfile. For reference, I got that line from this page: https://rubygems.org/gems/sqlite3/versions/1.3.11

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.