I closed the open source project alinesno cloud service

The beginning of the project is probably 18 At the beginning of the year, it is convenient for me to study and set up a project , Technology sharing originally made for learning , Here is just a summary reference to explain the integration process of my team .

summary

After years of practice and project iteration , Summary of experience , There are also various pit summaries in the process , Including the trend of the enterprise , Team integration , Found a lot of design problems in the baseline （ The problem here is not technology , It's design ）.

In the later stage, the team continues to enrich and improve , Formed a large project warehouse , The whole warehouse has become very large , At the same time, multiple projects and components are integrated under the subdirectory , Nearly hundreds maven engineering , Pictured ：

Reason for closure

It is easy for enterprises and teams to take extreme routes , And produce a lot of internal friction , And the problem of this process , To go back , Is less 2 year , More needs 3-5 Years of time .

Of course , Another way is the continuous reconfiguration of architects in the process , This is feasible , But for small and medium-sized teams , The cost of refactoring and architects , And the cycle cost is very large , Especially when switching architects or core personnel , Unless you can completely master the whole design idea .

But even so , Iteration of old and new projects , And maintenance , It will also consume at least more than half a year of internal resources , Old and new project migration , Especially the projects produced on .

For enterprises and teams ,1-3 Years are the cycle of development , Internal friction generated , The internal friction here is not just the internal friction of the project , And the team , Direction , company , Strategy, etc , Further development in the later stage is easy to fall behind , Especially in the current situation of rapid digitization .

Retention reason

For more directional learning and reference , Because the original design documents still exist , Compared with the document and code , You can learn further , It is helpful for newcomers , But cutting into the actual project is not very recommended .

At the same time, it is also considered to pass the design documents and relevant materials , You can do it later at your convenience , Search directly for , At the same time, there is a historical significance in the process . At the same time gitee Of GVP project , I didn't know the operation rules of open source projects , Shut down for a while , For users who are concerned about it and users who are learning , also gitee The impact of the platform has not been thoroughly considered .

Other

For the continuous expansion of the middle stage warehouse , At the same time, it also reflects that the historical burden of Zhongtai library has become heavy , On 21 In the year , In order to better cut into the digital construction and follow up the development of the industry , Split the middle stage , From the original Tai Chung Tai , Small front desk , Turned into Light middle platform , Small front desk , Large platform Structural thought adjustment .

Documents to be sorted ： I summarize some experience of the whole R & D process

Original project address （ It is recommended to learn to use ) ：https://gitee.com/landonniao/linesno-cloud-service