Diving into Some Common Architectural Patterns

In the previous chapter, we recognized the importance of software changes and will extend the discussion on how we should respond to these changes later in the book. The good thing is that we also learned how to work with existing approaches and patterns in the present context, alongside the evolution of requirements. If we were to open a forum on API design and architecture, we would find many discussions around the monolith. We now seek to decompose applications into more minor, decentralized services.

When discussing technical solutions, the truth is that there is no silver bullet. We must research and learn about the best options to fit our needs. When talking about new approaches and technologies, we need to understand that time will tell whether they are trustworthy and on which kinds of systems they work best. As a result, these new patterns bring many challenges and shifts in mindset. From state management and asynchronous...