Internet technology development as the main responsibilities of the technical team, building its technology management system should have the following objectives:
Operation and maintenance system
Code Management
- Engineering and management system, and access permissions.
- Branch creation, consolidation principles.
CI / CD
- Every time the code can trigger an automatic submission package, the release version of the test environment, automated testing.
- Product managers can select a test environment version, designated as the release version into a production environment, confirmed automatically published to the production environment without operation and maintenance manual.
cloud service
- Make full use of all types of Paas cloud platform services, such as SMS, map bed, and file systems, improve the stability of basic services, and reduce maintenance costs.
- Databases exemplary cloud database as far as possible, rather than self constructed on ECS.
Containerized
- Build a deployment environment mirroring each different technology stack.
- According to certain principles of various types of containers will be deployed on different servers.
- The complexity of service is determined whether or incorporated K8S only simple container.
- Try not to deploy or save the data in the container, must be deployed, you need to set the volume to ensure data persistence.
Capacity telescopic
- For the system load, there must be an automatic monitoring and early warning mechanisms.
- Under the circumstances, to select manual or automatic handling system capacity expansion or reduction.
data backup
- Depending on the size of the data value, determine the frequency of backup and storage time of the backup file. You can restore the backup in emergency situations.
Technology Architecture
Separate front and rear ends
- All project realization or transformation of the front and rear ends of the splitter.
- All front-end engineering technology stack, back-end technology stack, as much as possible unified.
Architecture Selection
- Determine what works and infrastructure matching principle: a single point of server or micro-service system.
- Under each architectural choice of technology components clearly down, as much as possible unified, reasonably avoid different projects using different components to achieve common functionality.
Code review
- Code to introduce automated inspection tools, checks preferably integrated into the code CI / CD control is carried out.
- Have a manual review mechanism to ensure that the code achieve the structural problem does not occur.
test
automated test
- Interface-level automated testing is a necessity, we need to choose a good testing tools, as well as language use cases.
- Maintenance mechanism of automated test cases to date.
Manual testing
- Demand testing process, the problem record, test standards.
- Test plan templates and review mode.
- Test case design principles, methods, tools created based update is to use the system.
- Test execution process, requirements, based tools to perform recording.
- Test report template format.
File
- Front-end architecture documentation
- Back-end architecture documentation
- Database table structure explained
- Interface documentation
tool
- Code Management
- Automated Deployment
- Project management
- Knowledge Management
- Document Management