Hello, I’m Angelo Brandão! 👋

Table of Contents Introduction The Appeal of Shortcuts When the Library Does Much More Than You Need (Bloat) The Invisible Weight on Performance: Where Libraries Really Affect the Service 4.1. Initialization Overhead 4.2. Unnecessary Memory Consumption 4.3. Abstractions That Hide Costs 4.4. Accumulated Latency in Microservices Transitive Dependencies: The Silent Domino Effect Updating Is Easy — Until It Isn’t How to Decide If It’s Worth Using a Lib Best Practices to Reduce Risks Conclusion 1. Introduction In modern development, it’s almost natural to turn to external libraries for productivity gains. They reduce rework, accelerate delivery, and allow teams to focus energy on what truly generates value. However, this decision, which seems simple and pragmatic at first, carries a frequently ignored consequence: each import brings with it a future cost, especially when it comes to production performance. ...

Introduction to Event-Driven Architecture with KEDA and RabbitMQ The need to build scalable and reactive systems has increasingly led teams to adopt the Event-Driven Architecture (EDA) model. Instead of relying on direct integrations between services, communication is done through asynchronous events, which reduces coupling and improves overall performance. In this practical guide — a true KEDA RabbitMQ tutorial — you will learn to: Implement an event-driven audit microservice Integrate RabbitMQ as a message broker Configure KEDA to automatically scale consumption on Kubernetes Table of Contents What is an Event-Driven Architecture 1.1. Benefits of Event-Driven Architecture 1.2. Communication Flow Technologies and Tools Used Proposed Scenario: Event-Driven Audit Microservice 3.1. Overall Solution Flow Event-Driven Project Structure with RabbitMQ and KEDA Step-by-Step Implementation 1️⃣ Running RabbitMQ Locally 2️⃣ Creating the Audit Microservice 3️⃣ Deploying the Service on Kubernetes 4️⃣ Configuring KEDA for Autoscaling with RabbitMQ Testing Autoscaling on Kubernetes Best Practices and Observability Conclusion — Advantages of Event-Driven Architecture with KEDA and RabbitMQ References and Further Reading 1. What is an Event-Driven Architecture An event-driven architecture is based on the idea that each relevant action within the system (such as creating an order or updating a record) generates an event. These events are published to a queue and processed independently by interested services. ...

Table of Contents Why Spring Boot Changed Java Development? What You Will Learn Setting Up Creating the Project: Three Possible Ways Understanding the Project Structure The Main Class: The Heart of the Application Running for the First Time Creating Your First REST API Working with JSON: The Modern Web Standard Creating a Resource List Customizing Configurations Organizing Code: Layered Architecture Next Steps in Your Journey Golden Tips for Beginners Complementary Resources Conclusion 1. Why Spring Boot Changed Java Development? Imagine being able to create a complete web application in Java without having to configure dozens of XML files or getting lost in complex configurations. This was exactly the dream of every Java developer a few years ago — and Spring Boot made it a reality. ...

Introduction Anyone who develops microservices knows: failures happen. Dropped connections, slow external services, congested queues — all of this can compromise a system’s availability. Quarkus, in addition to being fast and optimized for native Kubernetes environments, already comes with support for resilience features through MicroProfile Fault Tolerance. This means we can apply classic fault tolerance patterns to our applications with just a few annotations. In this article, I’ll show you how to implement these patterns practically, with code examples and tips that can save your application in production environments. ...