Low code of the trilogy

In the field of software development in recent years, low-code has been touted to the sky. It seems that you have never been exposed to low-code and you are embarrassed to say that you work in the software field. In fact, it is not necessary. A large part of this is capital.Part of the result is the emergence of new technologies, and some people who play with words have created a new name. I should have been developing in this area more than 10 years ago, so I wanted to summarize low-code for a long time. During the Spring FestivalI didn't go back to my hometown, just to sort out, there are three articles in total, namely cause, realization, and future. This article is the third article, summarizing the future trend of low-code.

The low-code vision is very beautiful, but it is not clear how to develop in the future, but it can be explained from the aspects of usage scenarios and technical solution requirements

Scenarios

Currently, the main ways of using low-code are mainly, as a module auxiliary way, as a whole system with low-code implementation. These two ways

1, auxiliary type

This method is generally combined with the main system in the form of a module or subsystem. Low-code mainly implements local business requirements and page definitions, such as page design, process definition, rule definition, document local definition, etc., to assist the main business system.Such systems generally have complex business requirements, and it is difficult to fully implement them simply by relying on low code.

2, integral type

The overall method can realize the display class or simple business system, and it can be implemented with low code, such as our common questionnaires, Q&A, small company portals, product promotion pages, etc., or to collect and display information.The system can be fully implemented with low code.

Technical solution requirements

Although low-code can realize functions without development, the needs of each customer are ever-changing, and it is difficult to fully consider the needs of various application scenarios. This requires low-code systems to have scalability, allowing customersYou can have secondary development capabilities on this platform, and technically provide rich API interfaces.

If the low-code is SAAS, data security, resource competition, performance, secondary expansion and other issues need to be considered. This requires the design of the underlying architecture. Don't take one step at a time. In the end, the demand cannot be realized or even pushed downCome back, what a good price

Technology needs to be considered more, especially for secondary expansion, other such as high performance, high availability, security, etc. should also be paid attention to

Currently low-code is hot, but what it will eventually develop depends on the implementation of the scene. Of course, the implementation of requirements cannot be separated from the realization of technology, which requires more technical consideration and solution design.More comprehensive

If you like it, remember to pay attention~