<?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 Mathias WOLFF</title><link>https://www.blog-des-telecoms.com/tags/postgresql/</link><description>Recent content in PostgreSQL on Mathias WOLFF</description><generator>Hugo</generator><language>fr-FR</language><copyright>&lt;a href="https://www.blog-des-telecoms.com"&gt;Blog des télécoms&lt;/a&gt; © 2009 - 2026 by &lt;a href="https://www.linkedin.com/in/mathias-wolff-47a7941/"&gt;Mathias WOLFF&lt;/a&gt; is licensed under &lt;a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;CC BY-NC-SA 4.0&lt;/a&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;</copyright><lastBuildDate>Thu, 16 Jul 2026 12:18:14 +0200</lastBuildDate><atom:link href="https://www.blog-des-telecoms.com/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>Mise en pratique, React + Go (Gin / GORM / PostgreSQL)</title><link>https://www.blog-des-telecoms.com/blog/mise-en-pratique-stack-react-go-postgresql/</link><pubDate>Thu, 30 Jul 2026 09:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/blog/mise-en-pratique-stack-react-go-postgresql/</guid><description>&lt;p&gt;&lt;em&gt;Article 6 de la série &amp;ldquo;De la spécification à l&amp;rsquo;exécution&amp;rdquo;. Cinq articles plus tôt, j&amp;rsquo;ai posé la spec, les rôles, la mesure et le property-based testing. Il reste à voir à quoi ressemble le workflow sur une vraie pile.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Je prends ici un stack volontairement courant. React côté front, Go avec &lt;a
 href="https://gin-gonic.com/"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;Gin&lt;/a&gt;, &lt;a
 href="https://gorm.io/"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;GORM&lt;/a&gt; et PostgreSQL côté back. Le cas d&amp;rsquo;usage est simple. C&amp;rsquo;est justement ce qui le rend utile. Le &lt;a
 href="https://github.com/mwolff44/spec-to-tests"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;repo public&lt;/a&gt; contient un boilerplate runnable dans &lt;code&gt;examples/billing-react-go/&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Practical Implementation: React + Go (Gin / GORM / PostgreSQL)</title><link>https://www.blog-des-telecoms.com/en/blog/practical-implementation-react-go-postgresql-stack/</link><pubDate>Thu, 30 Jul 2026 09:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/en/blog/practical-implementation-react-go-postgresql-stack/</guid><description>&lt;p&gt;&lt;em&gt;Article 6 of the series &amp;ldquo;From Specification to Execution.&amp;rdquo; Five articles earlier, I established the spec, roles, measurement, and property-based testing. Now, we need to see what the workflow looks like on a real stack.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m intentionally using a common stack here. React on the frontend, Go with &lt;a
 href="https://gin-gonic.com/"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;Gin&lt;/a&gt;, &lt;a
 href="https://gorm.io/"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;GORM&lt;/a&gt;, and PostgreSQL on the backend. The use case is simple. That&amp;rsquo;s exactly what makes it useful. The &lt;a
 href="https://github.com/mwolff44/spec-to-tests"
 
 
 class="link--external" target="_blank" rel="noreferrer"
 
&gt;public repo&lt;/a&gt; contains a runnable boilerplate in &lt;code&gt;examples/billing-react-go/&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>