<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Exygen</title><link>https://www.exygen.fr/en/tags/development/</link><description>Recent content in Development on Exygen</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright (c) 2020 - 2023, Exygen; all rights reserved.</copyright><lastBuildDate>Sun, 09 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.exygen.fr/en/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>persistence-js: the future persistence layer of Exygen applications</title><link>https://www.exygen.fr/en/blog/2026/08/09/persistencejs/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.exygen.fr/en/blog/2026/08/09/persistencejs/</guid><description>
&lt;p&gt;Every Exygen application needs, sooner or later, the same thing: describe a data model, persist it to a database, evolve it without breaking production, and query it cleanly from code. Until now, each application reinvented its own data access layer. &lt;strong&gt;persistence-js&lt;/strong&gt; puts an end to that.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;In TypeScript/Node, you often have to choose between two bad options: a raw SQL layer (fast, but where you hand-write every &lt;code&gt;INSERT&lt;/code&gt;/&lt;code&gt;UPDATE&lt;/code&gt; and recompute relations everywhere), or an ActiveRecord-style ORM (entities that inherit from a base class, implicit change tracking, and switching database engines that is nearly impossible in practice).&lt;/p&gt;</description></item></channel></rss>