Workflow mode description-Process Control Mode (2) -- Parallel split

1. Theoretical Model

This mode is actually the and model we often come into contact.

It is worth noting that this definition is generally concurrent between B and C, and the implementation is generally two different threads/processes. As far as I know, many companies that develop workflow engines still do not have this and concurrent branch concept, and there are still many such cases. If you are interested, you can take a look at the fact that many e-government approval processes are selected based on order and conditions, and "parallel approval" is rarely used.

2. digress

This mode is also a basic branch method. A workflow engine with a slight reputation can be directly implemented. In China, achieving this model seems to be a sign of a company's "Technology Poverty Alleviation.

What is technology poverty alleviation "?

In small and medium-sized software enterprises in China, practitioners have a strong feeling that the structure required is equal to the software structure. Because of our talent gap, from the demand to the software layer-System Analysis and system design, there is basically no one to take responsibility. As a result, this fault gradually disappears from the coding process.

The implementation of parallel approval is a little complicated and indirect. Technically speaking, concurrency is involved in the management of this concurrent thread/process. For example, how to organize and manage these concurrent units and how to notify the interaction of different concurrent units, it also takes into account complicated details such as waiting for a machine in the middle, restarting and restoring, resource competition, concurrency conflicts, and deadlocks. These technical details are not directly reflected by actual business needs.

If the company has insufficient technical knowledge, it will be more afraid of the problems brought about by concurrency. What's more serious is that the leadership suffers from strategic myopia and it will feel that these things at such a cost cannot be directly reflected in the actual business, it is better to directly degrade actual needs into sequential and conditional selection modes (based on past practical experience, especially in our e-government field, it is also a bad option to degrade to a sequential mode in many cases ). In addition, the business design of concurrent processes also requires careful consideration of the details of work coordination. This seems to be a variety of adverse factors, the cost of achieving such a parallel branch is so high, it may not have a good impact on the application of the actual project (these effects, especially in reducing costs and improving customer satisfaction ). This type of company generally works as a white-collar employee at a blue-collar level. (sighs, this represents the current situation of the Chinese software industry. This is the case for most small and medium-sized enterprises ).

Obviously, the above idea is common in small companies, especially in the management style of business operations. Therefore, if a company is willing to invest money to implement this concurrency model, I think the company can show at least three aspects of its "Technology Poverty Alleviation ": first, the Team has technical strength to solve the problems caused by concurrent applications, and second, the leadership realizes the growth potential of some indirect things; then, this group obviously has a connection between the requirement and the encoding, and does not simply map the requirement structure directlyCodeStructure.

In my opinion, it is more important to understand this industry from the surface.

3. Application

This is a very flexible model. This mode is very simple. However, this mode is introduced into a whole process, especially for businesses with other restrictions, which can extend the complex process structure.

Technically, synchronous merge, asynchronous merge, selection of authenticator, and thread merge may occur in the future for a concurrent and branch (these modes will be introduced later ), if we introduce the loop mode on the branch (which will be introduced in the future), we need to consider every detail accurately.

In terms of business, the design of a concurrent process involves the allocation, exclusive, and competition of actual resources. Project communication and coordination required for parallel work is also a business process that requires careful consideration.

however, this mode seems simple, and it is complicated to use in combination with other modes and with the constraints of actual business conditions. Therefore, we will only briefly introduce this mode here. We will explain it in detail later when we introduce other matching modes. This topic does not belong to any mode. Therefore, a column Article will be opened later.