The Accuracy of Code, the Wisdom of the Samurai: Mastering the Path of Software Development
Reusable solution to a recurring problem in software design. Guides best practices, promoting efficiency, maintainability, and effective problem-solving in various contexts.
In recent times, I have observed a series of events that make me reflect on the use and abuse of microservices. Below, I will describe the events that led me to reconsider the tools I typically use when designing an application’s architecture. Perhaps this will also help you reflect on your development habits.
Connecting frontend apps to backend services is a vital task in the tech world. There are effective strategies for this. We’ll explore the Backend For Frontend (BFF) design pattern, commonly used in distributed systems and microservices.
Migrating from monolithic apps to efficient ones is a widespread software challenge. Fortunately, there’s a proven strategy that can guide this process, known as the Strangler Fig Pattern. Coined by Martin Fowler, this pattern outlines a gradual approach to migrating a application by iteratively transferring its functionality to a new system. The end result is a more readable, maintainable, and feature-rich application that aligns with modern technology trends.
Microservices architecture offers the advantage of breaking down an application into small, decoupled services, with each service owning the data it manages. However, a challenge arises when generating a transaction involving multiple services. To address this issue, the SAGA pattern is employed.
As Tolkien wrote, “One Ring to rule them all, One Ring to find them, One Ring to bring them all and in the darkness bind them”. Software architecture arise when creating a project with the intention of addressing all current and anticipated code organization problems. However, some programmers tend to use the same architecture that worked for them in previous projects, assuming it will work in the current one, but that is not always correct.
