


The impact of an enterprise's organizational structure on its technical architecture
Introduction | Technical personnel often have a tendency to focus on digging coal (working on technical architecture) without understanding the context of coal mining (the business background and organizational structure of the company). They do not know the organizational structure, business background and technology of the company. There is an implicit mapping relationship between architectures, and this relationship sometimes directly determines the success or failure of technical architecture transformation. |
This article attempts to establish this contextual background for technical personnel (especially architects), improve the technical personnel's vision, and allow technical personnel to promote the improvement and upgrading of the system architecture on the premise of understanding the enterprise's business background and organizational structure, with a view to Be more successful.
Economic BackgroundThe picture below is called the bathtub curve, which comes from Niels Pflaeging's book "Organize for Complexity" [Appendix 2]. It mainly reflects the changes in the Western economic model from the last century to the present. The shape looks like a bathtub, hence the name.
- The period before 1900 was called the pre-industrial era, also known as the handicraft era. The main body of value creation in this era was craftsmen who mastered skills. Highly dynamic, localized markets, and customization were the main characteristics of the market in this era.
- The period from 1900 to 1980 is known as the Taylor Industrial Age. The main body of value creation in this era was machines. The market was vast and slow, with little competition. Improving efficiency and competing for low costs through mechanization and large-scale production were the main focus of the market in this era. Features.
- 1980 is now called the post-industrial era, also known as the global economic era. The main body of value creation in this era is knowledge workers. Emerging industries continue to exert competitive pressure on traditional industries. They are highly dynamic and continue to respond quickly to market demand. The key to success in this era of markets.
The organizational structure cannot be simply designed by the leadership. Different economic models require different organizational structure support. There is an implicit mapping relationship between the organizational structure and the economic model.
The picture above is the mainstream Taylor-type organizational structure in the Taylor Industrial Era, also known as the Command & Control organization. The leadership of the organization observes the market and formulates target plans, which are passed down by middle-level managers and implemented by lower-level employees.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
The Taylor Industrial Age lasted for more than a century and had a profound impact on our society. Even today, Taylor-type organizations are still the mainstream organizational structure of various enterprises in our society.
The picture above is a beta-type organization that is gradually emerging in the post-industrial era. It is common in some emerging industries such as mutual benefit network business companies. This type of organization still has leaders who focus on observing the market and formulating shared goals and constraints, but the organizational structure is relatively flat and the team organization favors cross-functional mixing and collaboration to respond quickly to market changes.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
Beta-type organizations are a model of modern leadership models and the direction of learning and transformation for many, especially traditional companies.
The complex adaptive organizational structure in the picture above, also known as the control feedback organizational structure (Cybernetic Organization), is currently relatively rare among established companies (only seen in a few startups), but it is a new trend in future organizational structures. This structure does not have centralized goal setting. The cross-functional mixed and collaborative team directly connects with the market, continuously communicates with the market to obtain needs, and responds quickly and flexibly to market changes.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
Mel Conway proposed the so-called Conway's Law [Appendix 3] in 1967, which pointed out that there is an implicit mapping relationship between organizational structure and system architecture:
Organization which design systems […] are constrained to produce designs which are copies of the communication structures of these organizations.
The design of the organization of the design system is equivalent to the communication structure between organizations
Conway's law can also be stated in reverse:
Conway’s law reversed: You won’t be able to successfully establish an efficient organization structure that is not supported by your system design(architecture).
You cannot build an efficient organizational structure if your system architecture does not support it. You can't build an efficient system architecture if your organizational structure doesn't support it.
Conway's Law gives us a good inspiration. There is an implicit mapping relationship between system architecture and organizational structure. You cannot unilaterally change the structure of one side, and both sides must be linked when adjusting. As shown in the figure below, if the system architecture is monolithically coupled, it will be difficult to organize a decentralized cross-functional market-oriented team structure. The two sides cannot be mapped, and friction and fights between teams are inevitable. Therefore, we generally first decouple and split individual applications according to business line boundaries, and at the same time make corresponding organizational structural adjustments. This is the motivation behind the microservice architecture that has become popular in recent years.
Technical architecture cannot exist and be designed unilaterally independently. It has an implicit mapping relationship with the organizational structure and supports the core driving elements of the organization. The following two figures respectively illustrate the core architecture driving elements of Taylor-type organizations and complex adaptive organizations, as well as the resulting application architecture characteristics.
From the technology stack and application architecture characteristics adopted by an organization, you can also quickly infer the organization's business model and organizational structure, as shown in the figure below. Monolithic architecture, centralized database, and layered architecture are common in Taylor-type organizations; while cloud computing, REST microservices, and DevOps technologies are common in Beta and complex adaptive organizations. The figure below also reflects the synchronous evolution trend of organizational structure and technology stack.
- We have entered the post-industrial era, and organizations need to adjust their structures to adapt to new market changes. Complex adaptive architecture is the evolutionary trend of future organizational architecture.
- There is an implicit mapping relationship between the market, organizational structure, system architecture and technology, which cannot be simply designed and unilaterally adjusted. Qualified architects must have insight into this mapping relationship, systematically and flexibly promote organizational and system architecture adjustments based on market and organizational status quo, align enterprise business, organization and technology, and respond to market changes more agilely.
- Without changing the enterprise's organizational structure and management culture, it is difficult to unilaterally change the enterprise's technical architecture. In the end, the technical architecture will be constrained by the strong organizational structure and enterprise management culture, reflecting the enterprise's management culture and organizational structure. (This article does not talk about corporate management culture, but corporate management culture is also crucial to corporate architecture).
- In the digital transformation of an enterprise, the adjustment of the system architecture and the enterprise's organization and management culture must be carried out simultaneously, and the key is the transformation of the enterprise's organizational and management culture structure.
The above is the detailed content of The impact of an enterprise's organizational structure on its technical architecture. For more information, please follow other related articles on the PHP Chinese website!


For years, Linux software distribution relied on native formats like DEB and RPM, deeply ingrained in each distribution's ecosystem. However, Flatpak and Snap have emerged, promising a universal approach to application packaging. This article exami

The differences between Linux and Windows in handling device drivers are mainly reflected in the flexibility of driver management and the development environment. 1. Linux adopts a modular design, and the driver can be loaded and uninstalled dynamically. Developers need to have an in-depth understanding of the kernel mechanism. 2. Windows relies on the Microsoft ecosystem, and the driver needs to be developed through WDK and signed and certified. The development is relatively complex but ensures the stability and security of the system.

The security models of Linux and Windows each have their own advantages. Linux provides flexibility and customizability, enabling security through user permissions, file system permissions, and SELinux/AppArmor. Windows focuses on user-friendliness and relies on WindowsDefender, UAC, firewall and BitLocker to ensure security.

Linux and Windows differ in hardware compatibility: Windows has extensive driver support, and Linux depends on the community and vendors. To solve Linux compatibility problems, you can manually compile drivers, such as cloning RTL8188EU driver repository, compiling and installing; Windows users need to manage drivers to optimize performance.

The main differences between Linux and Windows in virtualization support are: 1) Linux provides KVM and Xen, with outstanding performance and flexibility, suitable for high customization environments; 2) Windows supports virtualization through Hyper-V, with a friendly interface, and is closely integrated with the Microsoft ecosystem, suitable for enterprises that rely on Microsoft software.

The main tasks of Linux system administrators include system monitoring and performance tuning, user management, software package management, security management and backup, troubleshooting and resolution, performance optimization and best practices. 1. Use top, htop and other tools to monitor system performance and tune it. 2. Manage user accounts and permissions through useradd commands and other commands. 3. Use apt and yum to manage software packages to ensure system updates and security. 4. Configure a firewall, monitor logs, and perform data backup to ensure system security. 5. Troubleshoot and resolve through log analysis and tool use. 6. Optimize kernel parameters and application configuration, and follow best practices to improve system performance and stability.

Learning Linux is not difficult. 1.Linux is an open source operating system based on Unix and is widely used in servers, embedded systems and personal computers. 2. Understanding file system and permission management is the key. The file system is hierarchical, and permissions include reading, writing and execution. 3. Package management systems such as apt and dnf make software management convenient. 4. Process management is implemented through ps and top commands. 5. Start learning from basic commands such as mkdir, cd, touch and nano, and then try advanced usage such as shell scripts and text processing. 6. Common errors such as permission problems can be solved through sudo and chmod. 7. Performance optimization suggestions include using htop to monitor resources, cleaning unnecessary files, and using sy


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

SublimeText3 Linux new version
SublimeText3 Linux latest version

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

Dreamweaver Mac version
Visual web development tools
