<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matteo Pampana on Medium]]></title>
        <description><![CDATA[Stories by Matteo Pampana on Medium]]></description>
        <link>https://medium.com/@matteopampana?source=rss-52ad1757c0f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sceP9Y6EHkCTOXMZAN_DuQ.png</url>
            <title>Stories by Matteo Pampana on Medium</title>
            <link>https://medium.com/@matteopampana?source=rss-52ad1757c0f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:59:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@matteopampana/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Time Breaks Your Tests? This Is A Simple Solution]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/time-breaks-your-tests-this-is-a-simple-solution-47b630621bcf?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1338/1*VxborMUPDc6j2Xf015oHSw.png" width="1338"></a></p><p class="medium-feed-snippet">The Art Of Mastering The Time With Tests In Go</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/time-breaks-your-tests-this-is-a-simple-solution-47b630621bcf?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/time-breaks-your-tests-this-is-a-simple-solution-47b630621bcf?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/47b630621bcf</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[time]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Fri, 29 Nov 2024 08:01:58 GMT</pubDate>
            <atom:updated>2024-12-01T18:45:56.745Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How I Create Beautiful Functions With 30+ Parameters]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/how-i-create-beautiful-functions-with-30-parameters-5b4d818371df?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/2600/0*1Q2SwymKwUHUW16i" width="5774"></a></p><p class="medium-feed-snippet">A roller-coaster journey from awful to excellent</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/how-i-create-beautiful-functions-with-30-parameters-5b4d818371df?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/how-i-create-beautiful-functions-with-30-parameters-5b4d818371df?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b4d818371df</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[go]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 23:15:05 GMT</pubDate>
            <atom:updated>2024-12-03T08:02:19.033Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Spectacular Design Tools To Better Communicate Your System Designs]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/3-spectacular-design-tools-to-better-communicate-your-system-designs-371c0d3d54e0?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1600/1*QZiW02RQL6qCd7TBgcK1qw.jpeg" width="1600"></a></p><p class="medium-feed-snippet">I use these three powerful tools to make me understand</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/3-spectacular-design-tools-to-better-communicate-your-system-designs-371c0d3d54e0?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/3-spectacular-design-tools-to-better-communicate-your-system-designs-371c0d3d54e0?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/371c0d3d54e0</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[drawing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Fri, 22 Nov 2024 10:23:21 GMT</pubDate>
            <atom:updated>2024-12-03T08:03:08.297Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Understanding Iterators In Go 1.23]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/understanding-iterators-in-go-1-23-eac5308dd49b?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1338/1*VbRHdP4dHSN8c1gfBUACDw.png" width="1338"></a></p><p class="medium-feed-snippet">Pills of Go: Iterators</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/understanding-iterators-in-go-1-23-eac5308dd49b?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/understanding-iterators-in-go-1-23-eac5308dd49b?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/eac5308dd49b</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[iterators]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[pills-of-go]]></category>
            <category><![CDATA[go]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 11:59:13 GMT</pubDate>
            <atom:updated>2024-12-02T08:20:41.645Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Splitting Batches Manually? Not Anymore With Go 1.23]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/splitting-batches-manually-not-anymore-with-go-1-23-49b01b79cd82?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1338/1*VYOa42-wRo-wJkc5nsrJrg.png" width="1338"></a></p><p class="medium-feed-snippet">Pills of Go: Slices are getting better with this function in Go 1.23</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/splitting-batches-manually-not-anymore-with-go-1-23-49b01b79cd82?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/splitting-batches-manually-not-anymore-with-go-1-23-49b01b79cd82?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/49b01b79cd82</guid>
            <category><![CDATA[batch-processing]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[chunk]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Fri, 15 Nov 2024 20:13:54 GMT</pubDate>
            <atom:updated>2024-12-01T18:46:45.389Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[7 Reasons To Consider Go As Your Backend Language]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/7-reasons-to-consider-go-as-your-backend-language-4aee611b60a0?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1338/1*HNvVJIx_RupWMmxS02oAkg.png" width="1338"></a></p><p class="medium-feed-snippet">This is why we chose Go in our company</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/7-reasons-to-consider-go-as-your-backend-language-4aee611b60a0?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/7-reasons-to-consider-go-as-your-backend-language-4aee611b60a0?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aee611b60a0</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[go]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 19:00:45 GMT</pubDate>
            <atom:updated>2024-12-01T18:46:24.989Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Don’t Do This When Querying Your Microservice’s Database]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@matteopampana/dont-do-this-when-querying-your-microservice-s-database-860a34fa6a99?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/1338/1*Eq-GCrVA7xV_-bOPW04cKw.png" width="1338"></a></p><p class="medium-feed-snippet">&#x2026;plus 2 mistakes you must avoid when working for a company</p><p class="medium-feed-link"><a href="https://medium.com/@matteopampana/dont-do-this-when-querying-your-microservice-s-database-860a34fa6a99?source=rss-52ad1757c0f9------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@matteopampana/dont-do-this-when-querying-your-microservice-s-database-860a34fa6a99?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/860a34fa6a99</guid>
            <category><![CDATA[pull-request]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Wed, 13 Nov 2024 13:01:15 GMT</pubDate>
            <atom:updated>2024-12-02T08:21:12.320Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Struggle to Strength: 3 Powerful Ways to Design Better Software Architectures]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://levelup.gitconnected.com/from-struggle-to-strength-3-powerful-ways-to-design-better-software-architectures-68d4f13aa566?source=rss-52ad1757c0f9------2"><img src="https://cdn-images-1.medium.com/max/2600/0*4iDxf8RNHK5-TmEc" width="6016"></a></p><p class="medium-feed-snippet">Things that I do when I struggle to design software architectures</p><p class="medium-feed-link"><a href="https://levelup.gitconnected.com/from-struggle-to-strength-3-powerful-ways-to-design-better-software-architectures-68d4f13aa566?source=rss-52ad1757c0f9------2">Continue reading on Level Up Coding »</a></p></div>]]></description>
            <link>https://levelup.gitconnected.com/from-struggle-to-strength-3-powerful-ways-to-design-better-software-architectures-68d4f13aa566?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/68d4f13aa566</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Tue, 05 Nov 2024 17:38:54 GMT</pubDate>
            <atom:updated>2024-11-05T17:38:54.919Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[99% Increase Your Database Local Testing Time By Using This]]></title>
            <link>https://medium.com/@matteopampana/99-increase-your-database-local-testing-time-by-using-this-0a9f9fd3b10d?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a9f9fd3b10d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Fri, 02 Aug 2024 11:15:16 GMT</pubDate>
            <atom:updated>2024-08-02T11:15:16.209Z</atom:updated>
            <content:encoded><![CDATA[<h4>Initialize Your Local Data In a Smarter Way</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gs-_IhzVf-f3MOzX" /><figcaption>Photo by <a href="https://unsplash.com/@marcsm?utm_source=medium&amp;utm_medium=referral">Marc Sendra Martorell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Yesterday, I wanted to test some database features.</p><p>I desired to experiment with features I do not usually use at work. One month ago, one of my colleagues showed me how <em>materialized views</em> can be the right solution for a certain set of problems: we had to perform a full-text search with lots of rows in a table. So, I decided to get my hands dirty and verify his affirmations.</p><p>In these cases, I like to create a PoC (Proof-of-Concept) to familiarize myself with the features of Postgres I want to learn. To put down a realistic test, I decided to recreate, on my machine, a scenario similar to the one that I had in production.</p><p>So, I ran a docker image with the same version of the Postgres engine I have in production. I create a table with the same columns, and… suddenly, a problem knocked at the door of my curious brain…</p><p><strong>How is it possible to initialize the local DB, quickly?</strong></p><p>I did not want to misuse my time writing a script just to initialize millions of rows in my database. I want to spend time on learning how to exploit that feature of Postgres.</p><p>I also did not want to duplicate the same row millions of times because I needed some partition logic to generate the materialized views.</p><p>Some years ago, maybe I would have stopped here.</p><p>This time, I asked a friend how to tackle this issue, and he strongly answered: <strong>Ask ChatGPT! (Or any Generative AI you are using.)</strong></p><p>I decided to follow the advice. I rolled up my sleeves and I put down this prompt structure:</p><ul><li>business context</li><li>schema of the table</li><li>call to action with requirements</li></ul><p>I asked something like:</p><pre>(business context) We have a Postgres table that contains the information on ads that we need to show on our website. <br>Our website is a marketplace. <br>We sell items for houses, electronics, jewelry, wristwatches, cars, bikes, and motorbikes.<br><br>(schema) This is the schema:<br>| UUID | advertiser_name | category | title | description |  <br><br>(CTA + requirements) Give me the FULL SQL to fill the table with:<br>- 10 different advertisers<br>- every advertiser has an average of 800 items, which belong to 3 categories on average. <br>- The generated titles and the descriptions must be written in English and match the category (use real brands in the descriptions).</pre><p>The GenAI answered me with an SQL script in a matter of seconds.</p><p>I desire to spotlight here that I have been able to perform a complementary activity without losing focus and time. This is huge.</p><p>Do you know that research study that proves that after losing focus you need 23 minutes to get it back? Exactly, you get the point.</p><p>This is my take on LLMs. I think this is how we should use these tools. They can become our assistants, and we can delegate them the things that can harm our flow and cause us to lose a lot of time.</p><p>What are your thoughts? Let me know in the comments</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a9f9fd3b10d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Think About Microservices]]></title>
            <link>https://levelup.gitconnected.com/what-i-think-about-microservices-5f650d4a1c49?source=rss-52ad1757c0f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f650d4a1c49</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Matteo Pampana]]></dc:creator>
            <pubDate>Tue, 16 Jul 2024 16:45:20 GMT</pubDate>
            <atom:updated>2024-11-05T17:10:09.059Z</atom:updated>
            <content:encoded><![CDATA[<h4>Let’s Demystify Microservices Together</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O5ySENWsa0QGRrpF" /><figcaption>Photo by <a href="https://unsplash.com/@anritikhon?utm_source=medium&amp;utm_medium=referral">Andrey Tikhonovskiy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I have been working for years at a company that extensively uses this type of architecture, and I want to write about some things I have learned during this time.</p><p>There is a lot of hype behind this type of architecture, and I have decided to share with you what is really behind this choice. What you might face if you follow the <em>buzzword</em> of the moment, and whether it is the right solution for your problem. <strong>Or not</strong>.</p><p>In this article, I will talk about:</p><ul><li>What a microservice is;</li><li>Why use microservices;</li><li>And, how “micro” your microservices should be.</li></ul><h3>What is a microservice?</h3><p>A microservice is a cohesive piece of software that you can release and scale independently, where one or more functionalities reside.</p><p>The key concepts here for me are:</p><ul><li><strong>cohesive</strong>: you cannot (you can, but you would be wild) write a microservice that handles both payments and login;</li><li><strong>one or more functionalities</strong>: it is not true that a microservice = one functionality. Microservices may implement many functionalities, as long as they are cohesive.</li></ul><h3>Why microservices?</h3><p>The reason often lies in the organization of development teams and the need to scale functionalities differently.</p><p>It does not make sense to talk about microservices if there are no specific traffic needs or organizational requirements (multiple developers on the same codebase). Why? Because microservices <strong>will increase the complexity</strong> of your system. And you want to keep that low, right? Right?</p><p><strong>So, are you telling me I can structure a system without microservices? Yes!</strong> <em>Modular monoliths exist, and I recommend you look into what they are. If you are creating your startup alone or with a few collaborators, avoid the idea of starting with microservices. In this case: Modules YES, Microservices NO.</em></p><p>Let’s get back to us. You started with your beautiful monolith (modular, right?). If you notice that one of these modules (or components) has high traffic, instead of scaling everything, you can decide to make a smarter move.</p><p>In fact, scaling the entire application vertically or horizontally would be a waste of resources. You have 5% of your application generating 99% of your traffic. Do you really want to scale the remaining 95%?</p><p>So, you only extract the module that generates 99% of the traffic. Congratulations, you have created a <strong>microservice</strong>. Now, you can release that module independently from the rest of the monolith and scale it to handle traffic spikes, responding to your users in a flash.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*Rpzn9oI3eliioqUxllqs-w.png" /></figure><p>Another factor that might trigger your desire to create microservices is organization. Imagine you want to have teams highly specialized in specific strategic domains of your business.</p><p>Do you want a team focused solely on payment development? You create a service dedicated to payments. Do you want a team focused only on login? You create a service dedicated to login. And so on…</p><p><strong>Note</strong>: <em>we are talking about services, not repositories</em>. You can have multiple services and a single repository (monorepo). Alternatively, you can have N repositories for N services.</p><p><em>This is an additional dimension you can explore.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fHCTruCnb04o7Djn" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=medium&amp;utm_medium=referral">Annie Spratt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>How BIG a microservice should be?</h3><p>It depends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DJ5EOAiQI7wb-At4" /><figcaption>Photo by <a href="https://unsplash.com/@tonnnyj?utm_source=medium&amp;utm_medium=referral">tian dayong</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What happens if you make tiny microservices?</h3><p>You have created a microservice with only one function. It only handles login with username and password. OAuth2.0 is handled by another microservice.</p><p>Here, we are talking about the microscopic level. We are at the bare minimum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*25QXepy0x2Jvtofc" /><figcaption>Photo by <a href="https://unsplash.com/@gabiontheroad?utm_source=medium&amp;utm_medium=referral">Gabriella Clare Marino</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Having such a small microservice certainly has advantages:</p><ul><li>Coherence</li><li>Clear responsibility</li><li>Very readable</li><li>Reduced codebase</li><li>Therefore, it is easy to maintain (the single microservice)</li></ul><p>But…</p><ul><li><strong>Network requests increase</strong> (latency). If you divide a system into tiny components, you will have a lot of components—a lot of components that will eventually want to communicate with each other. Good luck! :)</li><li><strong>Your teams will need to communicate more frequently</strong> to develop new functions.</li><li><strong>Data consistency can become a problem</strong> (eventual consistency to the extreme). If you adopt a solution with a distributed database relative to the microservices, you will face problems. Latency increases, data propagation time increases, and you will only sometimes have the most updated data in the database of micro X.</li><li><strong>Possibility of encountering distributed transaction problems</strong>. Do you have a distributed database? Great! Actually, it could be better! Suppose you have one service responsible for verifying a user’s identity and another for registering the user. In that case, you must ensure they inform each other of the outcome before giving the new user the green light.</li><li><strong>Difficult to maintain</strong> the total set of services (the system) if you do not have many developers.</li></ul><p>In short, an extreme approach in a “small” organization leads to management difficulties for the services that can make the evolution and maintenance of the system challenging.</p><p>Indeed, this approach makes it easier to maintain the evolution and maintenance of a single component.</p><p><strong>Remember</strong>: <em>The more you segment your system into separate components, the greater the complexity; the greater the complexity, the more effort is required to deliver a new product feature! Balance is key.</em></p><h3>What happens if you make big microservices?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KZc6gvL2qVM--GLT" /><figcaption>Photo by <a href="https://unsplash.com/@_staticvoid?utm_source=medium&amp;utm_medium=referral">Lucas Santos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A play on words: microservice and large. But it’s not. Some call them “miniservices.”</p><p>These microservices (or miniservices) work well in small companies with few employees. Why? Because in this way, you can split the codebase into a smaller number of components to manage and maintain.</p><p>Moreover, you have fewer network calls, which can help mitigate latency and data consistency issues.</p><p>Miniservices are often the most suitable approach for organizations with few developers. It is counterproductive to have 1,000 microservices and 20 developers.</p><blockquote>Let me put it better: maintaining high quality, high delivery speed, and expecting one developer to manage, evolve, and maintain 50 microservices alone is definitely counterproductive!</blockquote><p>On the other hand, dividing less means having larger services and, therefore, more <strong>internal</strong> complexity. Having larger services can mean having to work on two distant components simultaneously.</p><p>When adopting a “large” microservices (or miniservices) approach, you must know how to divide well. You need to know <strong>how to set boundaries</strong> between one module and another. How do you choose a module? What is something independent to you? Studying some principles of <strong>Domain Driven Design</strong> could help answer these borderline philosophical questions.</p><p>The extreme of this approach is having a single modular <em>microservice</em>. That is <strong>the modular monolith</strong> mentioned above. But writing “microservice” positions better in terms of <em>marketing</em> 😏</p><h3>Conclusions</h3><p>To conclude, what I have learned working in a company that uses this type of architecture is that you can’t have everything. The important thing is to find the most functional compromise for your project and your requirements and to remain flexible in your choice—without dogmas.</p><p>Are you at the beginning (low traffic) and have very few developers? Do not use microservices. You should use a modular monolith. Emphasize <strong>modular</strong>! This approach will reduce costs and complexity while you are already prepared to divide if necessary (you have the modules).</p><p>Do you have components with high traffic? Do you have particular needs to organize your developers very clearly? Identify the core domains of your business and create your micro (or mini) services. You choose the size. You can also mix the two approaches. Small services for particularly important things, larger ones for others. It’s up to you!</p><h3>Suggested Articles Of Mine</h3><ul><li><a href="https://medium.com/@matteopampana/learning-domain-driven-design-ddd-part-4-6ecc1f1f0c8d">Learning Domain-Driven Design (DDD) — Part 4</a></li><li><a href="https://blog.bitsrc.io/eventual-consistency-when-microservices-may-leave-you-speechless-a77f9c0bb24f">How To Think About Data Consistency in Monolithic and Microservices Architectures</a></li></ul><h3>Join the Discussion!</h3><p>If you have read the article until now, thanks! It means a lot to me. ❤️</p><p>Your experiences, insights, and opinions are invaluable.</p><p>👇 <strong>Drop your comments below, and don’t forget to follow me for more insights</strong>.</p><p>Feel free to connect with me on <a href="https://www.linkedin.com/in/matteopampana/">LinkedIn</a> for further discussions ✍️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f650d4a1c49" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/what-i-think-about-microservices-5f650d4a1c49">What I Think About Microservices</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>