Binary transport protocols in an analyst view
Binary communication protocols partially displace synchronous REST and message brokers. Developers often choose API and transport level protocols by their own view, but an analyst can't influence that, or he or she doesn't have enough experience in that area.
Therefore we could have typical problems:
- Insufficient requirements specs.
- Only "happy flow" realization.
- Lack of analyst competencies to consult QA and colleagues from related integrated systems.
This talk would be helpful for systems analysts in defining their mission in the development process using binary transport protocol gRPC.