preface

You know what the biggest headache of being an architect is, of course, drawing.

The most difficult graph to draw is what graph, called the current situation graph, before I saw an ant quit P7 code excreta mountain to describe the old code, I want to say that maintenance of these are not what, you have the ability to draw this excreta mountain try…

Having worked as an architect for several years, I have come to understand that the architecture diagram is full of beauty, and there is no architecture diagram that depicts the current situation like shit, because there is no architecture in the current situation. How can you ask me to draw a picture without architecture?

So if a boss asks you to draw a picture of the situation, let him draw his own.

The body of the

This article is written to clarify a soul problem I have encountered in the past few years as an architect. How to successfully buckle such a perfect architecture design on the mountain of excrement and then purify it? After years of buckle, I finally seem to have some flavor

“I licked my finger. It’s internal.”

Architecture design, status quo sorting two steps

As an architect, one of the main jobs is to understand the current situation of the business, and then make trade-offs and trade-offs in architectural design, to create a set of architecture suitable for the business and implement it, but this approach is limited to small teams and relatively less complex projects. When you undertake the architectural design work of a huge project jointly maintained by hundreds of front-end engineers and dozens of business lines, it is a little difficult to do so. After a period of practice, I find there is a way.

That is, first feel the outline of the business, and then start architectural design, put the business parts in a small area, design the business irrelevant parts first, and lock the business related parts into a specific layer, leave him alone.

On the other side, call together the architects of the core business development and the business line to start the mapping of the technical architecture governance. There are two main lines

  • The control increment
  • Combing the stock

The control increment

For incremental problems, such as the new project, new integration and docking, the technical reconstruction and so on carries on the strict review and control technology, the chief architect, you need to personally participate in the incremental evaluation and related meetings, and review of these projects and technical scheme to grasp the essence of “specification according to specification, no specification according to the existing methods, “Do not play new tricks “, be sure to control the incremental problems in the business in a controllable range, to avoid expanding the base of stock problems.

Combing the stock

The incremental end of a hammer sale, violent solution, the stock here will have to work slowly, one by one comb, according to your current design of the architecture expectations, preset landing conditions, such as falling a micro front-end architecture, may need to comb clearly

  • Based on the application definition in the microfront end, which business realities are currently out of bounds
  • How are different businesses embedded in the current situation
  • What capabilities the access party needs to provide for the connected application

The stock of carding should be carded based on the necessary conditions of architecture landing. In this way, once serious conflicts are found between the necessary conditions of architecture landing and the process of carding, it may be necessary to adjust the design scheme and consider how to solve the conflicts. Last picture

Screenshot 2020-06-23 5.27.09 PM

Identify the drop-off point in the architectural design

A set of architecture is bound to contain very complex layers and boundaries. After all, the implementation of architecture design is not like a seal, it is finished after one stamp. We need to find the landing point of the whole architecture, which is the part used to wrap the business in the whole architecture design.

Still based on micro front-end architecture, for example, the front-end architecture to be born, its core site is applied, namely the need to define clearly what application, the application for the control of the business is a what level, what lines of business to do modifications to will yourself into your architecture design, defined in the application in other parts of the architecture, application management, application management, Before launching, building, etc., landing must be done first. Only by converging the business to your defined application can you land the micro-front-end architecture you have designed

As the saying goes, all things are difficult before they are easy. If you step on a steady foot, you will not succeed in landing, but you will win at least half of it.

The latter

The implementation of architecture design is more a test of architect skills than architecture design itself, and the key points of this paper are mainly these

  • Architecture design, business information collection, both hands must be hard
  • Set the necessary conditions for the implementation of the architecture, and constantly match the business status before the implementation
  • Identify the location of the architecture, the business based unit
  • You can’t be too careful every step of the way, right

This article is formatted using MDNICE