potiuk commented on PR #27468:
URL: https://github.com/apache/airflow/pull/27468#issuecomment-1312930149

   > I stand corrected, the AIP was there and I missed the voting. So any 
argument I make below is mood.
   
   The JSON-RPC is actually up for discussion still. Until the founding PR (or 
even after - I think the way we will implement int the way that we will be able 
to replace the implementation in the future if we find this is not good. In the 
implementation proposal of @mhenc this is literally an implementation detail - 
and vast majority of changes will be to make sure we implement tests amd make 
sure all the calls are mapped. 
   
   This is because we are using "standard" HTTP stack rather than Grpc-like 
solution, because GRPC gets a bit more of a "tie-in" about the processing model 
for threading etc. And after a lot of reading and talking to some of my 
friends, and analysing issues - I tend to agree with @ash and @andrewgodwin  
that (among other issues), the threading model of GRPC is a big, unknown risk 
(Python Threads and GIL issues are still unsolved issue, and using proven set 
of backend fori/process-driven/gevent etc. approach is much more reilable, 
debuggable and scaleable). And JSON RPC is basically piggy-backing on that 
while providing a simple and standard semantics of mapping input/output 
parameters of methods. 
   
   I'd say - let's give it a try and see  from the final tests, if JSON-RPC is 
as good solution as we think it is, and we can revisit it later. Eventually the 
whole test harness and making sure that there are no DB methods left  and that 
some of the components of ours are truly db-less will let us move forward with 
it. Once we get it implemented, Replacing the internals of communication 
between the components will be far less of a problem.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to