processed), not the message returned by the function. An example is as follows: { "errorMessage": "rpc error: code = Unknown desc = Exception calling application", "errorType": "*errors.Err", "functionMessage": below: #!/usr/bin/env python3 #-*- coding:utf-8 -*- """ module to say hi """ def handler(event, context): """ function handler """ event['functionName'] = context['functionName'] event['functionInvokeID'] handle messages in JSON or binary format. An example is shown below: #!/usr/bin/env node exports.handler = (event, context, callback) => { result = {}; if (Buffer.isBuffer(event)) { const message = event

processed), not the message returned by the function. An example is as follows: { "errorMessage": "rpc error: code = Unknown desc = Exception calling application", "errorType": "*errors.Err", "functionMessage": #!/usr/bin/env python3 #-*- coding:utf-8 -*- """ module to say hi """ def handler(event, context): """ function handler """ event['functionName'] = context['functionName'] event['functionInvokeID'] handle messages in JSON or binary format. An example is shown below: #!/usr/bin/env node exports.handler = (event, context, callback) => { result = {}; if (Buffer.isBuffer(event)) { const message

processed), not the message returned by the function. An example is as follows: { "errorMessage": "rpc error: code = Unknown desc = Exception calling application", "errorType": "*errors.Err", "functionMessage": #!/usr/bin/env python3 #-*- coding:utf-8 -*- """ module to say hi """ def handler(event, context): """ function handler """ event['functionName'] = context['functionName'] event['functionInvokeID'] handle messages in JSON or binary format. An example is shown below: #!/usr/bin/env node exports.handler = (event, context, callback) => { result = {}; if (Buffer.isBuffer(event)) { const message

processed), not the message returned by the function. An example is as follows: { "errorMessage": "rpc error: code = Unknown desc = Exception calling application", "errorType": "*errors.Err", "functionMessage": below: #!/usr/bin/env python3 #-*- coding:utf-8 -*- """ module to say hi """ def handler(event, context): """ function handler """ event['functionName'] = context['functionName'] event['functionInvokeID'] handle messages in JSON or binary format. An example is shown below: #!/usr/bin/env node exports.handler = (event, context, callback) => { result = {}; if (Buffer.isBuffer(event)) { const message = event

Ø跨团队协作需要考虑技术栈落地成本 ü 参与团队分别使用C，Golang，Java等多种技术栈 Ø基于蚂蚁SOFA体系的Mesh化思考 ü 无法保证上下游应用同时升级到Mesh模式 ü 基于RPC内容的流量调度 ü 升级窗口有限，方案必须简单高效 Ø运维体系，容器化建设等方面适配 ü 蚂蚁运维架构建立在流量调度的基础上 ü 容器管理平台更替快速进行中 ØGolang 性能，成本评估符合蚂蚁实际需求2 Network线程模型 0.1.0 9 Client Listener Read / Codec Read / Codec Read / Codec accept Stream Event Handler Pool Server Server Server worker Write Write Write connect send write worker worker Read write send线程模型 0.2.0 9 Client Listene r Read / Codec Read / Codec Read accept Stream Event Handler Pool Server Server Server worker Write Write Write connect data write worker worker Read

ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call( ProtobufRpcEngine.java:503) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:989) at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:871) at org.apache.hadoop security.UserGroupInformation.doAs(UserGroupInformati on.java:1893) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2606) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Custom Authentication Inject Session Conf with Custom Config Advisor Handle Events with Custom Event Handler Manage Applications against Extra Cluster Managers Engine Side Extensions Extensions for Spark

ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call( ProtobufRpcEngine.java:503) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:989) at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:871) at org.apache.hadoop security.UserGroupInformation.doAs(UserGroupInformati on.java:1893) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2606) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Custom Authentication Inject Session Conf with Custom Config Advisor Handle Events with Custom Event Handler Manage Applications against Extra Cluster Managers Engine Side Extensions Extensions for Spark

Note that: Kyuubi supports custom event handlers w custom event handler, the user needs to implement org.apache.kyuubi.events.handler.CustomEventHan arg constructor. kyuubi.backend.server.exec.pool handlers. Note that: Kyuubi supports custom event han register a custom event handler, the user need org.apache.kyuubi.events.handler.Custo which has a zero-arg constructor. kyuubi.engine.flink.application of the async event handler thread pool will wait for a new task to arrive before terminating duration 1.7.0 kyuubi.event.async.pool.size 8 Number of threads in the async event handler thread pool int 1

Note that: Kyuubi supports custom event handlers w custom event handler, the user needs to implement org.apache.kyuubi.events.handler.CustomEventHan arg constructor. kyuubi.backend.server.exec.pool Note that: Kyuubi supports custom event han To register a custom event handler, the user n subclass of org.apache.kyuubi.events.handler.Custo which has a zero-arg constructor. kyuubi.engine.flink.application of the async event handler thread pool will wait for a new task to arrive before terminating duration 1.7.0 kyuubi.event.async.pool.size 8 Number of threads in the async event handler thread pool int 1

Subscribe RegisterService Mesh Meetup · BeiJing 业务部⻔门调⽤用链 微博Service Mesh实践 - WeiboMesh �5 RPC A WEB A 平台体系 RPC B WEB B Golang 服务 PHP 服务 OR服务 …… RestFul API 业务部⻔门 Motan ➢ 业务部⻔门语⾔言种类繁多 ➢ 微服务体系建设不不完善/重复 全⾯面/灵活可扩展 服务治理理Service Mesh Meetup · BeiJing 跨语⾔言服务化⽅方式对⽐比 �11 微博Service Mesh实践 - WeiboMesh Http代理理 RPC模块 Agent代理理 研发成本 低 ⾼高 中 维护成本 低 ⾼高 中 使⽤用成本 低 低 中 治理理功能 中 ⾼高 ⾼高 扩展能⼒力力 低 中 ⾼高Service Mesh Meetup Restful handler Registry cgi cgi HTTP http filter register discoverService Mesh Meetup · BeiJing 反向代理理特点 �33 微博Service Mesh实践 - WeiboMesh ➢ 提供HTTP/cgi provider，可扩展 ➢ HTTP框架⾃自动转RPC，业务⽆无需开发新RPC框架