As an Engineering Leader we need to make multiple technological choice keeping business , risk , availability, maintainability and performance factor in mind and lots of disagreement happens , but we should always try to back that with data .
One such instance that happened was , At my previous organisation we were creating a reward engine for credit cards , calculate rewards based on multiple events for that to process calculation in parallel we needed to select a workflow engine , So he had three choices either build our own , use an open source or use a Saas Product . I assiged this taks to a developer of my team to do research , get the load testing data and POC code , as a result of which after few days based on his finding we first concluded that building our own workflow engine require a lot of effort and maintainance as a result of we will as of now divert from our busienss goals . For a paid product when we did calculation it , it prooved out to be too costly when we estimated the cost based on load, so only option was between two open source technology airflow and temporal . He gave me a code walth thorugh and showed the throughout , performace and number wise airflow was doing better and he was also pushing for airflow , but on the other hand temporal numbers was not that bad and best thing was that its ease of use and low maintanianbility so I sugested to use temporal at that time the developer was not agreeing , I explained it that while choosing the technology number doesnot matter we need to think about maintainability , support and with ease how this can fit in our echo system , and have an unbiased opinion I included a senior developer from my team in the discussion with all the data regardig number and effort estimate and convinced the junior developer that lets use temporal.