Risks and Technical Debt
Technical Risks
| Risk | Description | Mitigation | Severity |
|---|---|---|---|
Ghana Post GPS API Reliability |
The Ghana Post Digital GPS address decoding service may have limited availability or incomplete coverage, causing location resolution failures. |
Implement fallback to Google Maps geocoding with manual coordinate entry. Cache previously decoded addresses locally. |
High |
Dual Map Provider Complexity |
Maintaining integrations with both Google Maps and Mapbox increases development and testing effort, and creates potential inconsistency in map behavior. |
Abstract map operations behind a unified location service interface. Define clear responsibility boundaries for each provider. |
Medium |
Supabase Vendor Dependency |
Reliance on Supabase for database and auth creates vendor lock-in risk. Service outages directly impact platform availability. |
Use standard PostgreSQL features where possible for data portability. Maintain database migration scripts. Evaluate self-hosted Supabase as backup option. File storage on GCS reduces the blast radius of a Supabase outage. |
Medium |
Cloud Run Cold Start Latency |
Serverless containers may experience cold start delays during periods of low traffic, impacting user experience for the first request after idle periods. |
Configure minimum instance counts for critical services (frontend, search API). Use Cloud Run’s CPU always allocated option for latency-sensitive services. |
Medium |
Payment Compliance Complexity |
PCI DSS compliance requires specific handling of payment data, ongoing audits, and restricted access controls that add development and operational overhead. |
Use a PCI DSS-certified payment gateway to handle all card data. Never store or process raw payment credentials in the platform. |
High |
ML Model Accuracy |
Property recommendation models may produce irrelevant results early on due to limited training data from the Ghanaian real estate market. |
Start with rule-based recommendations. Gradually introduce ML models as data volume grows. Implement user feedback loops to improve model quality. |
Low |
Network Connectivity in Ghana |
Users in Ghana may experience inconsistent internet connectivity, affecting platform responsiveness and map loading. |
Implement progressive loading, offline-capable features, compressed images, and consider PWA with service workers for critical functionality. |
Medium |
Regulatory Uncertainty |
Ghana real estate regulations may change, affecting required integrations with government bodies (Lands Commission, court systems). |
Design integration layer as modular connectors that can be updated independently. Maintain relationships with regulatory bodies for advance notice of changes. |
Medium |
Technical Debt
| Item | Description | Priority |
|---|---|---|
Template Placeholder Configuration |
The docToolchainConfig.groovy microsite configuration contains placeholder values (site-title, footer-email, etc.) that need to be replaced with actual Asta Homes values. |
Low |
Confluence Integration |
The Confluence publishing configuration references a placeholder server URL. This needs to be configured if documentation will be published to Confluence. |
Low |
OpenAPI Specification |
The configuration references a sample petstore API spec file. This should be replaced with the actual Asta Homes API specification once the API design is finalized. |
Medium |
Internationalization Framework |
Multilingual support (French, Twi, regional languages) is planned but not yet implemented. The frontend architecture should account for i18n from the start to avoid costly retrofitting. |
Medium |
Virtual Tour Infrastructure |
The virtual tour and 3D model feature is listed as a requirement but no technology choice has been made. This needs evaluation (e.g., Matterport, custom WebGL, third-party SDK). |
Low |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.