Over the past year I've had to come up to speed on this question for a project my company's working on, and I've found these resources extremely helpful: Todd Hoff's highscalability.com; Scalable Internet Architectures, by Theo Schlossnagle; and Building Scalable Web Sites, by Cal Henderson.Highscalability.com in particular will point you to many good presenations, tutorials, books, … “The design and architecture of the application should include all the security aspects according to the established requirements and standards. The result or output of the architecture design process is an architectural description. The general application related rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission. Application Architecture Principles. If there is a possibility of modifying requirements, then avoid making a large design for whole system. 70. While application architecture might be invisible to the users, the impact that architecture has on your overall application is enormous. 69. Design your application to be self healing when failures occur. 72. Simply stated, the axis is an imaginary line that is used to organise a group of elements in the design. This approach avoids the interdependency among components of system which helps in maintaining the system easy. Posted by . In diagrams or drawings, the axis is represented by a dashed line. High Availability All applications will publish availability targets that have been agreed upon with the business. The key to build a scalable and reliable application architecture is to base your architecture on strongly-defined tenets and well-established foundations. Design for self healing. Principles for cloud-native architecture The principle of architecting for the cloud, a.k.a. Key Design Principles Following are the design principles to be considered for minimizing cost, maintenance requirements, and maximizing extendibility, usability of architecture − Separation of Concerns Divide the components of system into specific features so that there is no overlapping among the components functionality. Naming conventions should be defined in advance. Solution architects are the designated experts responsible for a system’s architecture as well as the technical standards (inc. technologies, platforms, infrastructure) of a particular product. The exception management will be same throughout the system. Therefore the axis is the most basic & most common organizing among the architecture principles. A very short list contains more generic and ethereal principles, hindering practical applications. application architecture design principles. The Symmetry in Architecture: Application Documentation Applications must have architecture, design and runbook documentation. They set the vision and their analysis is key to the product’s successful definition, design, delivery and life-time support. 71. Usually, there are around 20 enterprise architecture principles that must be followed. This way, you can support rapid growth and massive scalability, while avoiding deployment nightmares, higher code maintenance costs, and keeping up with the business needs. The 12 Principles of Application Architecture for Digital Business and IoT Published: 29 January 2015 ID: G00263480 Analyst(s): Yefim Natis, Ross Altman Summary Digital business and the Internet of Things demand a new level of excellence in enterprise architecture principles and practices. Application SLA All applications will publish a SLA that has been agreed upon with the business. cloud-native architecture, focuses on how to optimize system architectures for the unique capabilities of the cloud. Capacity Management Traditional architecture tends to optimize for a fixed, high-cost infrastructure, which requires considerable manual effort to modify.