<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>adrianratnapala</author><text>&amp;gt; If you&amp;#x27;re using microservices and care about security, do yourself a favor and use a monorepo.&lt;p&gt;This seems like a strong reminder that &amp;quot;microservices&amp;quot; aren&amp;#x27;t really about having lots of independent little systems but are a different way of factoring your one big system.</text><parent_chain><item><author>ejcx</author><text>If you&amp;#x27;re using microservices and care about security, do yourself a favor and use a monorepo.&lt;p&gt;A lot of improving security is about changing things in small ways but across the entire fleet. If you have microservices without a monorepo you oftentimes need to make the same changes in potentially hundreds of places.&lt;p&gt;This makes it a lot easier to do things like enforce standards for repos. Code coverage. Testing. Unsafe function use. Repo sprawl makes microservice security very challenging, and it isn&amp;#x27;t mentioned in this blog post. Losing track of services and leaving specific services behind is not good.</text></item></parent_chain></comment><story><title>Securing Microservices</title><url>https://medium.facilelogin.com/securing-microservices-with-oauth-2-0-jwt-and-xacml-d03770a9a838</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>corpMaverick</author><text>yes, yes, a thousand times yes.&lt;p&gt;We implemented our services like this a few years back. It worked really nice. But in everything that I have read I have never seen any references to this practice. I didn&amp;#x27;t even know it was called &amp;quot;monorepo&amp;quot;. I was just assuming everybody was using multiple repos and we were weird.</text><parent_chain><item><author>ejcx</author><text>If you&amp;#x27;re using microservices and care about security, do yourself a favor and use a monorepo.&lt;p&gt;A lot of improving security is about changing things in small ways but across the entire fleet. If you have microservices without a monorepo you oftentimes need to make the same changes in potentially hundreds of places.&lt;p&gt;This makes it a lot easier to do things like enforce standards for repos. Code coverage. Testing. Unsafe function use. Repo sprawl makes microservice security very challenging, and it isn&amp;#x27;t mentioned in this blog post. Losing track of services and leaving specific services behind is not good.</text></item></parent_chain></comment><story><title>Securing Microservices</title><url>https://medium.facilelogin.com/securing-microservices-with-oauth-2-0-jwt-and-xacml-d03770a9a838</url></story>