...
- Reporting stack learning curve
- Access to v2 production data, access to discern semantics behind structure
- Effecting availability of eLMIS source system would be very very bad
- Re-introduce Kafka (as in learning curve?)
- Introducing Debezium
- Solve for aggregate root problem
- Stream join
- Aggregate root table
- Solve for aggregate root problem
- Reporting stack doesn't achieve robustness level we'd need
Next steps:
- Josh Zamor create a wiki project page thing
- Josh Zamor to re-word streaming pros for laymen - technical goal section's priorities
- Josh Zamor to add links on Kappa, Debezium aggregate roots, do a once over on doc for links
- Wesley Brown to add links to google docs (Josh Zamor to find what he can in meantime)
- Wesley Brown to followup with project goals, schedule, roles and responsibilities, travel?, etc. Logistics of project!
- Wesley Brown who are decision makers (essentially roles and responsibilities)? (e.g. specifically on streaming architecture, on data access, on processes)
- Chongsun Ahn (Unlicensed) to start on learning plan for reporting stack, Kafka, Kappa architecture, Debezium, challenges we need to solve for