Why is the choice of architecture so important when building web applications? What are the criteria for determining whether the architecture is good or bad? This article describes how to design a Web application architecture that supports your current needs without burying holes in the future.
Why is web application architecture important?
The Web application architecture includes the all software modules and components of 160ecd78c34da2, internal and external systems, and that constitute the application. In addition to addressing all business requirements at the beginning of development, the architecture also ensures that all non-functional requirements (such as maintainability and agility) are met.
A well-structured Web application architecture can ensure that your Web application can be extended to business needs, while ensuring that all concepts can be properly isolated and their mutual dependencies can be considered. In general, the architecture of the application can not only ensure normal operation on an independent system, but also should be able to integrate well with all other software.
What should a good web application architecture look like?
First, the architecture is aggregates multiple processes of many events. it is not static: otherwise you can only create an architecture full of knowledge. For example, affected by the epidemic, remote office has become popular from 2020. No one can predict the need for global lockdown and ensure that all employees must be able to remotely access each business service. But even in less disruptive years, there will be some new businesses, new use cases, and new tools. These factors will make you continue to iterate your core architecture.
If you know that your architecture must evolve iteratively, have you tracked dependencies between different parts of the application? If you must make changes, can you clearly state what changes need to be made? Can you minimize the impact?
The core benchmark of web architecture quality is the degree to which technical debt can be avoided. The so-called technical debt refers to the wrong decision made at the beginning of the project that leads to rework, which incurs time, effort, and financial costs. A good software architecture enables you to cope with inevitable changes without generating technical debt. So to some extent only time can tell whether your architecture is wise.
What is the cost of making mistakes?
The problem caused by structural errors is mainly technical debt. Due to poor architecture design, technical debt is rapidly escalating: any modification will have a significant impact on many different applications. Not being aware of future changes means that the new code will detonate all kinds of things in your application. Problems, while trying to fix these problems will introduce new problems. A simple application can easily become a complex and huge monster, making changes more difficult and time-consuming, and will greatly affect business innovation and iteration.
The core principles of a sound Web application architecture
In the figure below, in accordance with the so-called core business "entity" method, OutSystems is the basic component of the service you want to create. The purpose is to bring together the functions in the entire product portfolio. If you need to make changes, you only need to modify it once, and everyone can use it. Therefore, the goal of Outsystems is not a single application, but a combination of applications: only when a single service is reused in multiple applications, the entire platform can bring obvious benefits and reflect its value.
This article first published WeChat public account: Front-end Pioneer
Welcome to scan the QR code to follow the official account, and push you fresh front-end technical articles every day
Welcome to continue reading other highly praised articles in this column:
- Deep understanding of Shadow DOM v1
- Step by step teaches you to use WebVR to realize virtual reality games
- 13 modern CSS frameworks to help you improve development efficiency
- Quickly get started with BootstrapVue
- JavaScript engine work? Everything you need to know from call stack to
- WebSocket combat: real-time communication between Node and React
- 20 interview questions about Git
- depth analysis of Node.js console.log
- What exactly is Node.js?
- with Node.js in 30 minutes
- Javascript object copy
- Programmers have a monthly salary of less than 30K before the age of 30, so what should they do?
- 14 best JavaScript data visualization libraries
- 8 top VS Code extension plug-ins for the front end
- Node.js Multithreading Complete Guide
- 4 solutions to convert HTML to PDF and their implementation
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用。你还可以使用@来通知其他用户。