<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SQL Elastic Pooling on Erwin Staal</title>
    <link>https://staal-it.nl/tags/sql-elastic-pooling/</link>
    <description>Recent content in SQL Elastic Pooling on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Wed, 25 Nov 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/sql-elastic-pooling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Database per tenant infrastructure</title>
      <link>https://staal-it.nl/posts/db-per-tenant-catalog-database-infrastructure/</link>
      <pubDate>Wed, 25 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/db-per-tenant-catalog-database-infrastructure/</guid>
      <description>In the first post in this series, we&amp;rsquo;re going to talk about the infrastructure. We need some database server to host each tenant&amp;rsquo;s database and the shared database that contains information on all the tenants (like which database belongs to whom). We also need infrastructure to host the API on and off course, need something for configuration and secret management.
TL;DR: All templates and the pipeline can be found in my repository.</description>
    </item>
    
  </channel>
</rss>
