Application Architecture - Speed vs Scalability
Application design is an extremely important topic in software development. I see many people with no idea how to create a good architecture, which can create major complications as the system evolves — new features, new demands, problems, delivery pressure, and many other factors that contribute to increasing application complexity.
Entire systems can be rebuilt simply because the team failed to create a good architecture, or at least an ideal starting point that allows the project to evolve and adapt. This can happen for various reasons: lack of knowledge and pressure to deliver (very common). The latter creates a trap by assuming that skipping precious software development steps in the name of speed and delivery won't affect quality and scale.
In this article I'll cover some problems that can arise from not following a well-defined standard. My goal is to bring the software developer's perspective and things they should care about to mitigate future problems — for themselves and for the company.