Welcome to the inDrive Engineering Handbook repository, maintained by the inDrive Engineering Team. This repository is designed to serve as a comprehensive guide, outlining best practices and standards upheld by the inDrive team.
Handbook Purpose
The inDrive Engineering Handbook aims to establish and promote effective practices and shared standards, encouraging collaboration within inDrive and with the broader community. By removing barriers, optimizing workflows, and providing easy access to best practices, we support both internal projects and external contributions.
In this handbook, you'll find resources, templates, and tools intended to boost productivity and ensure consistency across all inDrive engineering.
How to Contribute
To contribute to this handbook, please refer to our guide: "Contributing to the Handbook". This section outlines our code of conduct and provides instructions for submitting pull requests to ensure a smooth and collaborative process.
Table of Content
About the Handbook
About inDrive
People
inSpire Framework
- inSpire Framework
- Quarterly Planning
- Development Cycle Management
- Program Management
- Team Meetings and Reviews
- Productivity Measurement Framework
Communication
Software Architecture
- Architecture Committee
- Architecture Standards
- Change Management Policy
- Technology Radar
- Service Tiering
- Backup and Recovery Policy
- Data Delivery Guarantees
- Data General Protection
- Observability Standard
- Personal Information Handling
- Primary Key Selection
- Universal Distribution of City and Country Setting
- Communication Patterns
- Parsing Protection Requirement
- Universal Entry Identifier
- Geo Distribution Principle
- Transactional Outbox
- Cold / Warm Storage for Services
Software Development
- Engineering Guidelines
Documentation Culture
- Documentation Workflow
- Documentation Types
- Documentation Hubs
- Documentation Guidelines
- Documentation Events
Glossary
Abbreviations and Acronyms
License
This project is open source and is licensed under the MIT License. For more details, please see the LICENSE file.