<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Platform Engineer on biancarosa.com.br</title><link>/tags/platform-engineer/</link><description>Recent content in Platform Engineer on biancarosa.com.br</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 19 Jan 2026 13:52:23 +0000</lastBuildDate><atom:link href="/tags/platform-engineer/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploying Modular Monoliths: One Codebase, Multiple Services</title><link>/posts/deploying-modular-monoliths-one-codebase/</link><pubDate>Mon, 19 Jan 2026 13:52:23 +0000</pubDate><guid>/posts/deploying-modular-monoliths-one-codebase/</guid><description>&lt;p>&lt;em>This post was originally published on my &lt;a href="https://backendengineeringadventures.substack.com/p/deploying-modular-monoliths-one-codebase">Substack - Backend Engineering Adventures&lt;/a>.&lt;/em>&lt;/p>
&lt;p>Last week, we talked about the anatomy of modular monoliths and how to structure them. But as you start to do that, issues arise, and one of the common question that you might think about but is afraid to ask out loud is: &lt;strong>can have an API and a queue consumer in the same service?&lt;/strong>&lt;/p>
&lt;p>And while you’re a free person, in a free world - meaning that you technically &lt;em>can&lt;/em> do this - you likely shouldn’t.&lt;/p></description></item></channel></rss>