Topics
Technical Task Priority Strategy
When we plan the tech tasks we are following the priciple:
Stability & Robust come first
Example:
Chaos Testing
Fault Injection
Rate Limiting
…
Correctness (on scale / distributed mode)
Example:
micro-services working well in multiple pods
Kafka consumer with multiple consumer instance
Distributed transaction support
Performance
Example:
NIO support
Distributed Cache
Efficient DB Query & index manangement
…
On-going common / architecture tasks
Observability
Monitoring:
Mobile
Mobile log integration
OpenTelemetry
Analytics
TM → SAF-51 - Getting issue details... STATUS
Temporal
GCP(database)
Kafka monitoring
Alerting on micro-services
Metrics design
Alertmanager management
Reporting
Grafana report https://grafana.com/docs/grafana/latest/dashboards/create-reports/
skedler https://www.skedler.com/
Genesys Integration
audit log
recording data storage
mobile chat
DLQ PoC
https://github.com/SafiBank/SaFiMono/pull/8819
Client side retry
DLQ Topic management
Log strategy & enhancement
Common Logger adoption
Common Logger enhancement
More log Level support
Auto logging with annotation support
Logging guideline & strategy
When to do logging
Log message format
Logger level management
Technical Code Review
We discussed the idea to have regular per squad technical code review, here are some pros & cons for this:
Pros
Technical Quality assurance
Tech Knowledge sharing
Tech debts detection
Code style consistency
Improved collaboration
Cons
Time consumption
Efficiency management
Actions
Get PII Data Definition
User b6b4a will contact data-privacy team to get the definition of PII data, then align with dev team to implement this in the logs
Setup Per Squad Daily Code Review Meeting
Dev leads will start to book per squad level code review meeting to have technical code review at daily basis. Gavin Zhang (Unlicensed) User 55816 zhenghong.li (Unlicensed) User 83c4d Alex Li Huang (Unlicensed) Enrico Benedict Quiñones (Unlicensed)