<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Active-Model-Serializers on Scholion</title><link>https://scholion.thluiz.com/tags/active-model-serializers/</link><description>Recent content in Active-Model-Serializers on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Sat, 21 Jun 2014 20:51:17 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/active-model-serializers/index.xml" rel="self" type="application/rss+xml"/><item><title>Avoid Rails When Generating JSON responses with PostgreSQL</title><link>https://scholion.thluiz.com/notes/avoid-rails-when-generating-json-responses-with-postgresql/</link><pubDate>Sat, 21 Jun 2014 20:51:17 -0300</pubDate><guid>https://scholion.thluiz.com/notes/avoid-rails-when-generating-json-responses-with-postgresql/</guid><description>The article argues that moving JSON generation into PostgreSQL removes expensive Ruby object creation and Rails serialization work, cutting response times and memory use for API payloads.</description></item></channel></rss>