Learn about scenarios and Solutions

Currently, a developer does not have many years of project development experience and may not have a deep understanding of the technology. After two years of work, I have been engaged in system development for a certain industry. The technology that may be used is basically fixed. A better project may be the optimization of the code framework in the future, it is encapsulated twice, the system is split into multiple modules, and the code framework is abstracted. Finally, the project is suitable for rapid development by many people. Finally, the business is monitored for operation.

However, most of the employees who can participate in these activities in the future are old employees. Of course, the requirements are high and technical businesses are well understood. However, this may also lead to project failure and re-development.

As an employee with insufficient development experience, I want to know some business scenarios and look at other people's solutions. I can think of a better solution. Through this process, I will study technology again. I personally feel good, regardless of the preceding scenario, the basic solutions are the same. The difference is that the detailed process of business processing is inconsistent.

For example, BPM-process monitoring, ESB-typical bus data exchange, ETL-typical data extraction, batch-Batch Processing (periodic rule mechanism ), drools-judgment mechanism queue-queue, cache-Cache Mechanism, which can be combined to provide a variety of solutions. The implementation mechanisms in these solutions are similar, however, they are only applicable to different scenarios.

At work, it is impossible to come into contact with these things. However, all the solutions and ideas at work are included in these scenarios. This is only a process that is not suitable for actual projects. However, as a developer, if you are not familiar with the scenario, you may have to learn how to optimize the project in the future. This is just a matter of time.

 

Recently, the project has gradually discovered that code optimization is not easy after the business is completed. For example, extjs is used in the previous section, but there are many project pages, many developers, one person is inconsistent with one code format, or a large number of paste copies, mechanical development, because it was not long before the company came, so in the middle and late stages, JS and the secondary encapsulation, but it was still pasted and copied, and there were still a lot of duplicates. Restructuring was demanding. But there is still a solution, which may not be good, but better than it is now. Based on struts, spring-JDBC, and a large number of SQL strings in the backend, I really don't have any good solutions (such complicated SQL statements are basically reports ), but is it necessary to make it into OLAP? The data volume is not large, the table sample is basically fixed, and functions such as exporting Excel and printing are also required. Currently, the only optimization is to regularly publish report data to form an intermediate History Table for storage, regularly publish report data, and save it into a table.

For businesses, complex business exchanges can all be split very finely. For crud of a single table, transactions are also based on simple configuration and there is no distributed problem. Although it is based on BS architecture, development for shared databases may sometimes involve FTP.