<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Now-Next — Insights</title>
        <link>https://now-next.nl/en/insights/</link>
        <atom:link href="https://now-next.nl/en/feed/postgresql.xml" rel="self" type="application/rss+xml" />
        <description>Field notes from building two SaaS products with AI agents. Concrete, with the numbers and the miscalculations included.</description>
        <language>en</language>
        <lastBuildDate>Mon, 28 Sep 2026 00:00:00 GMT</lastBuildDate>
        <item>
            <title>Invoice numbers per tenant in PostgreSQL, without gaps</title>
            <link>https://now-next.nl/en/insights/invoice-numbers-per-tenant-postgresql-without-gaps/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/invoice-numbers-per-tenant-postgresql-without-gaps/</guid>
            <description>Sequence, max()+1, SERIALIZABLE or a counter row: five ways to number invoices per tenant, measured under load in PostgreSQL 17 for duplicates, gaps and speed.</description>
            <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>PostgreSQL indexes for multi-tenant SaaS: tenant_id first</title>
            <link>https://now-next.nl/en/insights/multi-tenant-postgresql-indexes-tenant-id-first/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/multi-tenant-postgresql-indexes-tenant-id-first/</guid>
            <description>Five indexes, 1,000 tenants, one query, measured in PostgreSQL 17: why tenant_id goes first, what RLS does to the plan, and when partitioning pays off.</description>
            <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>Multi-tenant SaaS on PostgreSQL: six decisions</title>
            <link>https://now-next.nl/en/insights/multi-tenant-saas-on-postgresql/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/multi-tenant-saas-on-postgresql/</guid>
            <description>The six choices a multi-tenant SaaS locks into PostgreSQL: isolation model, RLS, indexes, money, restoring one tenant and migrating at scale. All measured.</description>
            <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>Row-level security in PostgreSQL: where tenants leak</title>
            <link>https://now-next.nl/en/insights/row-level-security-postgresql-tenant-isolation/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/row-level-security-postgresql-tenant-isolation/</guid>
            <description>Turning RLS on takes five lines of SQL. These are the five ways it is silently off afterwards, or leaks around the edges — each one measured in PostgreSQL 17.</description>
            <pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>Money in PostgreSQL: numeric, integer cents or money?</title>
            <link>https://now-next.nl/en/insights/money-in-postgresql-numeric-integer-or-money/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/money-in-postgresql-numeric-integer-or-money/</guid>
            <description>Which PostgreSQL type holds money exactly? numeric, integer cents, bigint and money side by side, with the pitfalls we tested and a query to audit your schema.</description>
            <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>Multi-tenant architecture: choosing an isolation model</title>
            <link>https://now-next.nl/en/insights/multi-tenant-architecture-isolation-models/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/multi-tenant-architecture-isolation-models/</guid>
            <description>Database per customer, schema per customer or one database with tenant_id and row-level security: the models side by side, and the three questions that decide.</description>
            <pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
        <item>
            <title>Multi-tenant from day one, or it never gets fixed</title>
            <link>https://now-next.nl/en/insights/multi-tenant-from-day-one/</link>
            <guid isPermaLink="true">https://now-next.nl/en/insights/multi-tenant-from-day-one/</guid>
            <description>Three decisions in a SaaS product are nearly impossible to reverse. Separating customers is the first, and the most expensive one to skip.</description>
            <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
            <category>SaaS architecture</category>
            <dc:creator>Chris van Eijk</dc:creator>
        </item>
    </channel>
</rss>
