https://diegogborges.github.io/Recent content on EXPONENTIAL DEV by Diego - Tech BlogHugo -- 0.152.2en-usThu, 04 Dec 2025 16:02:19 -0300https://diegogborges.github.io/posts/microservices-monoliths/Thu, 04 Dec 2025 16:02:19 -0300https://diegogborges.github.io/posts/microservices-monoliths/<p>Microservices or Monolith? Discover the strengths, the trade-offs, and the real-world lessons every developer must know before deciding how to start a project.</p> <ul> <li> <p><a href="#microservices-and-event-driven-architecture">Microservices and Event-Driven Architecture</a></p> <ul> <li><a href="#introduction-to-the-module-microservices-based-architecture">Introduction to the Module: Microservices-Based Architecture</a></li> <li><a href="#why-study-microservices">Why Study Microservices?</a></li> <li><a href="#what-you-will-learn-in-this-module">What You Will Learn in This Module</a></li> <li><a href="#why-this-module-matters">Why This Module Matters</a></li> <li><a href="#our-goal">Our Goal</a></li> </ul> </li> <li> <p><a href="#monolithic-systems">Monolithic Systems</a></p> <ul> <li><a href="#what-is-a-monolithic-system">What Is a Monolithic System?</a> <ul> <li><a href="#characteristics">Characteristics</a></li> </ul> </li> <li><a href="#teamwork-inside-a-monolith">Teamwork Inside a Monolith</a></li> <li><a href="#practical-benefits">Practical Benefits</a></li> <li><a href="#technological-constraints">Technological Constraints</a></li> <li><a href="#deployment-risks">Deployment Risks</a></li> <li><a href="#conclusion-about-monoliths">Conclusion About Monoliths</a></li> </ul> </li> <li> <p><a href="#what-are-microservices">What Are Microservices</a></p>https://diegogborges.github.io/posts/system-design/Thu, 04 Dec 2025 14:28:58 -0300https://diegogborges.github.io/posts/system-design/<p>In this article, we explore how System Design goes far beyond diagrams, serving as a practical framework for reasoning, justifying decisions, and building scalable, well-structured systems.</p> <h2 id="table-of-contents">Table of Contents</h2> <ul> <li><a href="#system-design">System Design</a> <ul> <li><a href="#introduction">Introduction</a></li> <li><a href="#understanding-the-core-concepts">Understanding the Core Concepts</a> <ul> <li><a href="#introduction-to-system-design">Introduction to System Design</a></li> </ul> </li> <li><a href="#what-is-system-design">What is System Design?</a></li> <li><a href="#why-is-system-design-important">Why is System Design Important?</a></li> <li><a href="#working-with-approximations">Working with Approximations</a></li> <li><a href="#example-of-system-design-reasoning">Example of System Design Reasoning</a></li> </ul> </li> <li><a href="#system-design-in-big-techs">System Design in Big Techs</a> <ul> <li><a href="#why-big-techs-use-system-design-in-interviews">Why Big Techs Use System Design in Interviews</a></li> <li><a href="#why-many-candidates-fail">Why Many Candidates Fail</a></li> <li><a href="#the-importance-of-deduction-and-approximation">The Importance of Deduction and Approximation</a></li> <li><a href="#system-design-in-the-real-world">System Design in the Real World</a> <ul> <li><a href="#why-system-design-is-essential-in-practice">Why System Design Is Essential in Practice</a></li> <li><a href="#justifications-and-trade-offs">Justifications and Trade-offs</a></li> </ul> </li> </ul> </li> <li><a href="#the-six-elements-of-system-design">The Six Elements of System Design</a> <ul> <li><a href="#introduction">Introduction</a></li> <li><a href="#six-fundamental-elements-of-system-design">Six Fundamental Elements of System Design</a> <ul> <li><a href="#1-requirements-gathering">1. Requirements Gathering</a></li> <li><a href="#2-capacity-planning">2. Capacity Planning</a></li> <li><a href="#3-data-modeling">3. Data Modeling</a></li> <li><a href="#4-api-modeling">4. API Modeling</a></li> <li><a href="#5-architecture-design">5. Architecture Design</a></li> <li><a href="#6-exploration--justification-trade-offs">6. Exploration &amp; Justification (Trade-offs)</a></li> </ul> </li> <li><a href="#the-value-of-the-process">The Value of the Process</a></li> <li><a href="#requirements-%E2%80%94-deep-dive">Requirements — Deep Dive</a> <ul> <li><a href="#core-features-and-domain">Core Features and Domain</a></li> <li><a href="#support-features">Support Features</a></li> <li><a href="#functional-vs-non-functional-requirements">Functional vs Non-Functional Requirements</a></li> </ul> </li> <li><a href="#next-steps">Next Steps</a></li> </ul> </li> </ul> <hr> <h1 id="system-design">System Design</h1> <h2 id="introduction">Introduction</h2> <p>In this new module, the focus is on <strong>System Design</strong>, an essential subject for anyone looking to advance in technology and system architecture.</p>https://diegogborges.github.io/posts/messaging-comparison/Tue, 02 Dec 2025 17:03:47 -0300https://diegogborges.github.io/posts/messaging-comparison/<p>This article provides a clear and concise comparison between RabbitMQ and Apache Kafka to help you choose the most suitable messaging solution for your system architecture.</p> <h2 id="table-of-contents">Table of Contents</h2> <ul> <li><a href="#objective">Objective</a></li> <li><a href="#history">History</a> <ul> <li><a href="#rabbitmq">RabbitMQ</a></li> <li><a href="#apache-kafka">Apache Kafka</a></li> </ul> </li> <li><a href="#solution-features-and-comparisons">Solution Features and Comparisons</a> <ul> <li><a href="#rabbitmq-features">RabbitMQ Features</a></li> <li><a href="#kafka-features">Kafka Features</a></li> </ul> </li> <li><a href="#consumption-strategy-pull-vs-push">Consumption Strategy (Pull vs Push)</a></li> <li><a href="#comparative-use-cases">Comparative Use Cases</a></li> <li><a href="#deployment">Deployment</a></li> </ul> <h2 id="objective">Objective</h2> <p>The objective of this article is to clarify doubts regarding which messaging system is most appropriate when implementing your applications. It analyzes RabbitMQ and Apache Kafka.</p>https://diegogborges.github.io/posts/rabbit-mq/Tue, 02 Dec 2025 16:53:48 -0300https://diegogborges.github.io/posts/rabbit-mq/<p>When you want to develop highly scalable distributed systems in several programming languages and one should communicate with others, it’s necessary an architecture with messaging queue systems and RabbitMq is one of the most used.</p> <h2 id="table-of-contents">Table of Contents</h2> <ul> <li><a href="#rabbitmq">What is Messaging</a></li> <li><a href="#rabbitmq">RabbitMQ</a></li> <li><a href="#how-rabbitmq-works">How RabbitMQ Works</a></li> <li><a href="#amqp-protocol">AMQP Protocol</a></li> <li><a href="#ack">ACK</a></li> <li><a href="#exchange-and-routing-key">Exchange and Routing Key</a> <ul> <li><a href="#fanout">FANOUT</a></li> <li><a href="#direct">DIRECT</a></li> <li><a href="#topic">TOPIC</a></li> <li><a href="#headers">HEADERS</a></li> </ul> </li> <li><a href="#channel">Channel</a></li> <li><a href="#publishing">Publishing</a></li> <li><a href="#listener">Listener</a></li> <li><a href="#stream">Stream</a></li> </ul> <h3 id="what-is-messaging">What is Messaging</h3> <p>Messaging is a communication mechanism between systems where one publishes the message and any other as a client receives the same, thus simplifying a lot in the development of distributed systems.</p>https://diegogborges.github.io/posts/rest-api/Mon, 17 Nov 2025 00:00:00 +0000https://diegogborges.github.io/posts/rest-api/<p>Everything you need to know to get started with REST in just a few minutes.</p> <p>REST API is the technology that transformed the way systems communicate with each other. It enables applications, websites, servers, and devices to exchange data quickly, securely, and universally — forming the foundation of modern apps, powerful integrations, and digital experiences that work anywhere.</p> <h2 id="index"><strong>Index</strong></h2> <ul> <li><a href="#-what-is-an-api">What Is an API?</a></li> <li><a href="#-what-is-a-rest-api">What Is a REST API?</a></li> <li><a href="#-key-rest-concepts">Key REST Concepts</a> <ul> <li><a href="#resources">Resources</a></li> <li><a href="#main-http-methods">Main HTTP Methods</a></li> <li><a href="#data-formats">Data Formats</a></li> </ul> </li> <li><a href="#-restful-api-characteristics">🔧 RESTful API Characteristics</a> <ul> <li><a href="#1-stateless">Stateless</a></li> <li><a href="#2-clientserver-architecture">Client–Server Architecture</a></li> <li><a href="#3-cacheability">Cacheability</a></li> <li><a href="#4-uniform-interface">Uniform Interface</a></li> <li><a href="#5-layered-system">Layered System</a></li> </ul> </li> <li><a href="#general-recommendations">General Recommendations</a></li> <li><a href="#use-plural-nouns-in-urls">Use Plural Nouns in URLs</a></li> <li><a href="#keep-the-base-url-simple-and-intuitive">Keep the Base URL Simple and Intuitive</a></li> <li><a href="#avoid-verb-based-urls">Avoid Verb-Based URLs</a></li> <li><a href="#use-http-verbs-to-operate-on-resources">Use HTTP Verbs to Operate on Resources</a></li> <li><a href="#resource-listing-and-detail-retrieval">Resource Listing and Detail Retrieval</a></li> <li><a href="#associations">Associations</a></li> <li><a href="#use-query-parameters-to-reduce-url-complexity">Use Query Parameters to Reduce URL Complexity</a></li> <li><a href="#error-handling">Error Handling</a></li> <li><a href="#versioning">Versioning</a></li> <li><a href="#partial-response">Partial Response</a></li> <li><a href="#pagination">Pagination</a></li> <li><a href="#actions-not-involving-resources">Actions Not Involving Resources</a></li> <li><a href="#multi-format-support">Multi-Format Support</a></li> <li><a href="#attribute-naming">Attribute Naming</a> <ul> <li><a href="#attributes-in-requestresponse-bodies">Attributes in Request/Response Bodies</a></li> <li><a href="#attributes-in-urls-query-parameters">Attributes in URLs (Query Parameters)</a></li> <li><a href="#attributes-in-headers">Attributes in Headers</a></li> </ul> </li> <li><a href="#references">References</a></li> </ul> <hr> <h1 id="what-is-an-api">What Is an API?</h1> <p>An <strong>API (Application Programming Interface)</strong> is a set of standards and protocols that allow different systems or users to interact with an application.<br> It enables clients to access the software’s features and services without needing direct access to its internal implementation.</p>https://diegogborges.github.io/about/Mon, 01 Jan 0001 00:00:00 +0000https://diegogborges.github.io/about/<h1 id="-welcome-to-my-site">👋 Welcome to my site</h1> <p>Hello! My name is <strong>Diego Gomes Borges</strong>, and this is my personal space on the internet where I share my journey, studies, projects, and insights about the world of <strong>Technology</strong>.</p> <p>After years of learning, building, experimenting, I decided to organize everything in one place — a clean, simple, and objective blog focused on <strong>high-quality tech content</strong>.</p> <hr> <h2 id="what-youll-find-here">What You’ll Find Here</h2> <h3 id="-programming">🧩 Programming</h3> <h3 id="-cloud">☁️ Cloud</h3> <h3 id="-devops--infrastructure">⚙️ DevOps &amp; Infrastructure</h3> <h3 id="-practical-projects">🛠️ Practical Projects</h3> <h3 id="-real-world-problem-solving">🐞 Real-World Problem Solving</h3> <h3 id="-quick-tips--utilities">⚡ Quick Tips &amp; Utilities</h3> <h3 id="-career--learning">🎯 Career &amp; Learning</h3> <h3 id="-code-challenges">🧠 Code Challenges</h3> <hr> <h2 id="-why-this-blog-exists">💡 Why This Blog Exists</h2> <p>Because useful technical knowledge should <strong>not</strong> get lost in random chats, notes, or memory.<br> This blog helps me <strong>organize what I learn</strong>, share it with others, and create a personal reference for future projects.</p>