<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Back-Pressure on Matheus Oliveira</title><link>https://blog.omatheusmesmo.dev/en/tags/back-pressure/</link><description>Recent content in Back-Pressure on Matheus Oliveira</description><image><title>Matheus Oliveira</title><url>https://blog.omatheusmesmo.dev/images/duke.svg</url><link>https://blog.omatheusmesmo.dev/images/duke.svg</link></image><generator>Hugo -- 0.146.0</generator><language>en-us</language><lastBuildDate>Sun, 01 Nov 2026 10:00:00 -0300</lastBuildDate><atom:link href="https://blog.omatheusmesmo.dev/en/tags/back-pressure/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside the Quarkus reactive core, part 3: a Uni is a recipe, not a result</title><link>https://blog.omatheusmesmo.dev/en/posts/mutiny-uni-recipe-not-result/</link><pubDate>Sun, 01 Nov 2026 10:00:00 -0300</pubDate><guid>https://blog.omatheusmesmo.dev/en/posts/mutiny-uni-recipe-not-result/</guid><description>Mutiny explained through tests: a Uni is a lazy recipe, the invoke that silently drops a Uni, retry as resubscription, why Mutiny does not schedule anything except with emitOn and runSubscriptionOn, why combine does not parallelize, failures as terminal events, demand and back-pressure, and the two TimeoutExceptions that look alike.</description></item></channel></rss>