1. What are Software Applications?
The 3-tier model is popular because it offers several advantages: modularity, scalability, and maintainability. Each layer can be developed and maintained independently, allowing smoother updates and modifications. Additionally, separating concerns simplifies the overall architecture and enhances system reliability.
2. Limitations of the Business 3-Tier Model
While the Business Logic/Persistence/Presentation layers paradigm for software applications is highly intuitive and was, undoubtedly, accurate in the remote past, it has become a gross and costly oversimplification of the reality of modern software.
Software engineers trained in this model tend to neglect other equally crucial aspects of application architecture and design, without which you would not have a viable product. This series of articles aims to rectify this situation by providing an alternative, sophisticated, and realistic view of modern application design.
Drawbacks of the 3-tier model
Below are some of the flagrant examples of oversimplification:
This series of articles will take another approach to examining application design, one that acknowledges the shortcomings of the 3-tier model and tries to replace it with a more modern approach.
3. Operational Excellence and Application Design
Operational Excellence, the central theme of this website, is defined as an organisation’s ability to steer its departments, products, and people effectively towards its vision.
For example, a mature and lucrative product has grown too expensive to run on-premise and requires redesigning to become more cloud-friendly. As with any transformation initiative, immense challenges can lie ahead. These challenges can be exacerbated by an antiquated view of technology and technical product design, leading to underestimating the effort and risks involved.
But this is not only about rare and expensive transformations. It’s also about the daily activities of software engineers. In the not-so-distant past, programming skills and business knowledge were enough to get most software developers through their day. Today, the complexity is so much more that gaps between performance expectations and the reality on the ground have become so significant they can’t be ignored.
What this series of articles aims at is offering multiple views, each from a slightly different angle, of a complex system where so much ingenuity, skill, and knowledge has been focused. It is like learning about the human body, described in terms of its constituent subsystems.
We hope these articles will allow software engineers to get closer to their work and become part of the drive to operational excellence without the frustration generally involved in performing a complex task effectively and efficiently.