An issue to track team knowledge transfer about Zync.

What will we do?

• Read the code first, trying to understand the most we can
• Going through models, queues, principles
• Writing some tests

Proposal

Deep dive into the code for 2 or 3 afternoons from 12/08 to 14/08

1. As homework: read the code, try to understand by yourself.
2. Explanation of:

• system/zync events, notification
• models
• entries
• queues
• locking mechanism
• interaction with external services (OpenShift, Keycloak)
  3. We will write as much as possible, tests in zync (as there are lacks of tests
  4. We will deep dive inside the recent Pull Requests, probably about generic REST adapter and the Openshift routes adapter (edited)

Recordings:

• Introduction: https://bluejeans.com/s/DjB2i
• Bug hunting: https://bluejeans.com/s/zsVJm
• Questions to Michal Cichra: https://bluejeans.com/s/9sFD8

So we would need to understand a bit more those topics:

• Deployment and CI/CD. Asking questions to operations
• Probably trying to use shipit by shopify https://github.com/Shopify/shipit-engine
• Understanding a bit que https://github.com/chanks/que
• Work with support about what they would like as debug tools: probably a REST API in zync
• Work with operations for more tools for performance/locking issues
• See also https://debezium.io