The front end of the source code: the initial address github
The rear end of the source code: the rear end address github
Individual work
Complete all database-related query interfaces, revision, and provides service class for the controller calls
Association Management System Requirements Analysis
As a leader, initially completed the division of labor, in order to consider cloud computing a big operation, consider using mongodb. Mongodb and complete a preliminary study. Mongodb also deployed the server, as well as there may be redis services, but also deployed redis. Use springboot selected as the back end. Mongorepository database connection as an interface of the basic operation. In deployment, the most trouble is encountered various maven jar package conflicts, the waste for a long time, and finally the use of someone else project configuration.
Second report
Learn the basic format similar jpa mongorepository, understand the basic grammar, a preliminary understanding of the similarities and differences between java and python decorators notes, test and realized its most basic class. Mongodb experience the benefits, in addition to the primary key field, which can easily modify table structure, can adapt to the needs of various modifications. But also began to step on the pit, he discovered the limitations mongorepository, the basic single-table can only modify the query to work.
Community management system design phase
FIG completion timing function, particularly the rear end started thinking about how to achieve better table structure, but also a complete embodiment of FIG. Complete database interface does not modify several basic classes. Mongotemplate started to implement some basic connection is working, and mysql is not the same, mongodb table joins more trouble, need to use more things, its flexibility in the field also gave me so much trouble. In particular, some fields are arrays, written original query. Unable to find mongotemplate like jdbc as the original query, but the use of his package interface provided by the various operations to be converted into the corresponding field. Encounter more problems, but also experience a java-like approach, we appreciate the convenience of the face of the object. They also found that all objects should lead to code a lot longer to improve the reading difficulty.
Prototype stage
He began to sprint. By a number of features not implemented. Complete front-end also realize their basic page. Started various interfaces docking. Modify the front end portion of page elements, resulting in a database field changes. Thanks mongorepository and mongodb, add fields very convenient, easy to modify all sorts of things. It should be implemented better service, basically a direct return to the java object you want. And implementation of controller classmates, fewer interface problems.
The final stage
Added functionality distal end, and a connecting portion complex table search functionality implemented troublesome. And the last shall be members of the association will be directly stored as objects. I encountered many problems, but to take direct method using java object storage, preservation of the object. Search only use basic regular expressions to achieve the basic functions, but corresponds to such a demand. The basic order was to meet demand. It should be functionally similar reasons, only tested a similar interfaces. Resulting in the latter part of the front also caused a lot of trouble. Also encountered a pit Critera of, OrOperator wording is incorrect, leading to not return the correct results.
Project Summary
Personal use of technology
| Use of technology | use |
|---|---|
| mongodb | database |
| mongorepository | Simple query and count |
| mongotemplate | Implement complex queries |
| Service | Provides an interface for the controller |
Reflections and Conclusions
I met the front and back interface definition inconsistent and so on, results in a modification of the portion of the database table. Also add a lot of workload. Front-end interface does not settle down, resulting in slow progress of the back-end. Waiting in learning more complex interfaces, in general, it did not too much of a drag on progress. Database should be adopted mongorepository, and generally do not need to add a field inquiry, in fact, there is not much change. However, their own design, add fields vary widely with the front end of the latter. The most progress was dragged front-end to achieve a page, but there is no corresponding documents, leading to the back-end can not move, can only achieve the first part of a simple query, as well as a list of interfaces. Documents delay, basically rely qq exchange, but also lead to some differences and problems, but also to re-implement a number of interfaces, increase the amount of duplication of effort. Database interface, usually relatively simple, similar interfaces only tested once, resulting in a number of interfaces there is a problem. Also increased the workload of front-end.
The development, the need to coordinate the front and rear end, as far as possible so that the front-end interface to do a good job, but also try to make the front-end interface to back-end lead. Such convenient front-end development, but also to the rear end out of time, but also better tested.
Suggest
- Encountered many technical problem of inadequate reserves, and select technical errors, can recommend technologies and frameworks before you begin.
- Individual projects play exercise less sense, more similar to the familiar with some basic ui. If the direct use of the command line, it would be more less, it is recommended to remove individual items, or force the use ui interface to adapt in advance how to provide the corresponding interface.