<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on BALES</title><link>https://bales.cc/en/posts/</link><description>Recent content in Posts on BALES</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>baptiste@bales.cc (Baptiste Lespinasse)</managingEditor><webMaster>baptiste@bales.cc (Baptiste Lespinasse)</webMaster><copyright>© 2026 Baptiste Lespinasse</copyright><lastBuildDate>Thu, 20 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://bales.cc/en/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture of VS Trivia</title><link>https://bales.cc/en/posts/vs-trivia-architecture/</link><pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate><author>baptiste@bales.cc (Baptiste Lespinasse)</author><guid>https://bales.cc/en/posts/vs-trivia-architecture/</guid><description>&lt;p&gt;From the very first steps in preparing the application, the requirements were clear: design a project that is both scalable and sustainable. It is in this spirit that I envisioned the infrastructure architecture. Whereas for my previous projects with more modest ambitions I opted for a standalone solution hosted on my VPS, this time I chose a distributed approach.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://bales.cc/posts/vs-trivia-architecture/featured.png"/></item></channel></rss>