-
Notifications
You must be signed in to change notification settings - Fork 2
Decisions
Maria Martinez edited this page Sep 18, 2026
·
1 revision
This section contains formal Architecture Decision Records (ADRs) capturing critical design choices, rationale, trade-offs, and consequences throughout the lifecycle of the Forest Client project.
When authoring a new ADR, use the following structure:
# ADR-[Number]: [Title]
- **Status**: [Proposed | Accepted | Superseded | Deprecated]
- **Date**: YYYY-MM-DD
- **Author(s)**: [Name(s)]
## Context
Describe the problem, requirements, constraints, and forces motivating this architectural decision.
## Decision
State the architectural decision clearly and unambiguously.
## Consequences
- **Positive**: Benefits, improvements, and problems resolved.
- **Negative / Trade-offs**: Added complexity, potential overhead, or operational requirements.| ADR | Title | Status | Date |
|---|---|---|---|
| ADR-001 | Adoption of Vue 3 Composition API and IBM Carbon Web Components for Frontend | Accepted | 2024-03-10 |
| ADR-002 | Reactive Architecture with Spring Boot 4 WebFlux and GraalVM Native Image | Accepted | 2024-05-15 |
| ADR-003 | Spring Integration Message Channel Architecture for Background Processor | Accepted | 2024-08-20 |
| ADR-004 | Dual-Database Model (PostgreSQL Modern Store + Oracle THE Schema Legacy) | Accepted | 2024-09-01 |
| ADR-005 | Gherkin / Cucumber BDD Automation Strategy for Community-Driven Cypress E2E Tests | Accepted | 2024-11-12 |
This wiki serves as the central documentation and knowledge base for the Forests Client Management System, maintained by the British Columbia Ministry of Forests.
Please Note:
- This wiki is a living document maintained by the development team and contributors.
- When making substantial architectural or code changes, remember to update the corresponding wiki documentation.
- Always verify critical environment configurations against team vaults and OpenShift secret managers.
Have questions, found a documentation discrepancy, or need clarification?
- Questions or Bug Reports: Open an issue in the GitHub repository
- Pull Requests: Submit code or doc improvements via Pull Requests
- Database Schema Reference: Explore our SchemaSpy ER Diagrams
Forest Client Wiki | GitHub Repository
- Architecture Overview
- Frontend Architecture
- Frontend Structure
- Backend Architecture
- Backend Structure
- Legacy Architecture
- Processor Architecture
- Data Model
- Development Overview
- Local Setup & Docker
- Frontend Setup
- Backend Setup
- Project Conventions
- Frontend Structure Guidelines