[ 
https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854682#action_12854682
 ] 

James Todd commented on AVRO-405:
---------------------------------

great points bo.

i took the approach of the protobuf codecs as the baseline and opted to not dig 
into the backing pipeline impl details. put another way, striving to "make it 
work" followed by "make it work right and make it work fast." definitely cut 
some corners. i would expect the netty impls to be efficient, though. on the 
other hand streamlining is not a bad thing.

thx for the test heads up! that's definitely a good one to work in.

yeah, likely over refactored the packages a bit. did that as a part of 
componentizing the impl given we are evaluating using this code inhouse. 
flattening things out is likely needed.

i did leave a note on #netty for trustin to given him a heads up, see if the 
codec part of this work should/could reside w/ netty/etc.

- james

> Netty-based Java RPC server
> ---------------------------
>
>                 Key: AVRO-405
>                 URL: https://issues.apache.org/jira/browse/AVRO-405
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: AVRO-405-for-review.patch, netty-avro.zip
>
>
> A nonblocking RPC server based on Netty should be more scalable than the 
> current implementation.
> We should provide two mechanisms for interfacing the RPC server to the 
> implementations:
> 1) "Blocking" RPC implementations run inside a worker threadpool. 
> Implementators would not know that they're working in a non-blocking context.
> 2) "Event-driven" RPC implementations that receive requests and some kind of 
> request context. They are responsible for eventually calling 
> context.respond(response) or somesuch. This would allow more scalable 
> interaction with downstream services.
> I propose we focus on (1) first.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to