<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>postgresql on jawr</title><link>https://jawr.github.io/jl-lu/tags/postgresql/</link><description>Recent content in postgresql on jawr</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© {year}</copyright><lastBuildDate>Mon, 25 Jan 2021 10:45:30 +0900</lastBuildDate><atom:link href="https://jawr.github.io/jl-lu/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>mx.ax - social schema distancing</title><link>https://jawr.github.io/jl-lu/blog/mx.ax-the-hows-and-why-of-the-database-schema-design/</link><pubDate>Mon, 25 Jan 2021 10:45:30 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/mx.ax-the-hows-and-why-of-the-database-schema-design/</guid><description>User isolation When creating a service that contains users who don&amp;rsquo;t require interaction with one other, it&amp;rsquo;s necessary to provide some assurances that their data will remain isolated. There are various strategies to try and ensure this isolation, each with their own benefits and issues. Below are the main ones:
Silo, each user has their own database instance. Bridge, each user has their own database (schema) on a shared instance.</description></item></channel></rss>