Avoiding anti-patterns in solution architecture
In this chapter, you have learned about a different way of designing solution architecture with various design patterns. Often, teams can drift away from best practices due to timeline pressure or the unavailability of resources. It is advised to try and avoid the following architecture design anti-patterns. An anti-pattern serves as an example of a poorly designed system:
- In an anti-pattern, scaling is handled reactively and manually. When application servers reach their maximum capacity and have no more resources available, users face disruptions in accessing the application. It’s only when users start reporting issues that the administrator becomes aware of the problem. The admin then initiates the process of launching a new server instance to alleviate the load on existing servers. However, there’s a drawback to this approach as there’s typically a delay of a few minutes between the instance launches...
