<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Minio on Shaaf's blog</title><link>https://shaaf.dev/tags/minio/</link><description>Recent content in Minio on Shaaf's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://shaaf.dev/tags/minio/index.xml" rel="self" type="application/rss+xml"/><item><title>A Quarkus minio tutorial - Store and retrieve objects from Minio</title><link>https://shaaf.dev/post/2025-04-02-a-quarkus-minio-tutorial-store-and-retrieve-objects-from-minio/</link><pubDate>Fri, 14 Mar 2025 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/2025-04-02-a-quarkus-minio-tutorial-store-and-retrieve-objects-from-minio/</guid><description>&lt;p>Consider a web application that needs to store user-generated content, such as images, videos, and documents. Instead of storing them in a file systems or using a database, the web application can use an object store. An object store can handle objects as a single unit, providing metadata about each object and abstracting away from the underlying storage which can be local or distributed. In this blog post I will explain a local setup for minio using docker. I also use Quarkus as the framework of choice for cloud native applications. and I use the minio SDK which is pretty awesome to work with together with Quarkus. Let&amp;rsquo;s do this :)&lt;/p></description></item></channel></rss>