Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Technical Standards
Conventions, best practices, and templates adopted by the Technology department at Patria.
Why standards matter
With a large system portfolio and multiple squads, standards are what guarantees:
- Consistency: code and documentation recognizable by any team member
- Quality: best practices built in from the start
- Speed: fewer decisions to make, more time to build
- Onboarding: new members learn the standards once and apply them everywhere
Sections
| Section | What you’ll find |
|---|---|
| Architecture | Principles, technology standards, data architecture |
| Code | Python, JavaScript, SQL standards |
| APIs | REST, events, versioning |
| Data | Naming, modeling |
| Security | Secrets, LGPD for devs |
| Templates | Ready-to-use templates for systems, runbooks, ADRs, postmortems |
Info
Standards are living documents: Standards evolve with the division. Propose changes via Pull Request with architecture team discussion.