What are microservices? Indeed, considered as an architecture, is an approach to building an application as a set of independently deployable services that are decentralized, decoupled and autonomously developed. These services are easily maintainable. While a monolithic is build as a single unit of work, microservices break that unit down

A domain-centric approach to organizing dependencies Clean Architecture Rules 1. Model all business rules and entities in the Core project 2. All dependencies flow toward the Core project 3. Inner projects define interfaces; outer projects implement them What belongs in the Core project * Interfaces * Aggregates * Entities * Value Objects * Domain Services

To create a data-driven culture is necessary and mandatory: initiate it, understand it, and do all employees make data-driven decisions. Collect information We need to collect every data entry in the company. All the information we have, we must store and process it. Measure everything Here we have to measure

The most amazing stage of my life as a programmer has been working as a tech leader. Having a team on my charge has been awesome. Next I will explain some learnings about this role. Your performance is the performance of the team. You have assignments and your success will

Is an extra layer that we add to our architecture and helps as a bridge between the modules that consume an API. Thus, we avoid that the clients send requests directly to the backend. Acting as an intermediary, we can add more functionalities like security, access policies and so on.

Is it a methodology? No, I do not say that because it is not as broad or strict as it sounds. Nor is a recipe. It really is a teamwork or a set of suggestions to give a quick solution. If you have a problem, this will guide you to

What is a distributed system? A distributed system, as its name implies, is a system which its components are located on different places (servers) on a network, these can be physical servers or virtual like a containers, but they are configured to reach the communication between them and the final

Many times I've asked myself the same question, Is the observer pattern the same as pub-sub pattern? Well, It isn’t. The Observer pattern is a software design pattern in which an object, named the subject, maintains a list of its dependents, called observers, and notifies them automatically

SOLID is an acronym that contains five design principles in the software development. * Single Responsibility principle * Open-Closed principle * Liskov Substitution principle * Interface Segregation principle * Dependency Inversion principle > The author Robert C. Martin warns without good design principles, the software becomes rigid, fragile, immobile and viscous. The broad goal is

Data Transfer Object (DTO) is an object that helps us to move data between components. What are the problems about our complex objects? * Strong coupling between the client and the domain. * Strong coupling between the client and the database. * More complexity of the client side. * Multiple requests in the same

I mean the blog. Although this is my first post, maybe blogging should have been my first step to start my career to establish the main advice I've learned. Although I haven't finished my journey, I think that I have started to write a couple of