Logical Plan Logical Plan Optimized Logical Plan Physical Plan Program API Analysis rules Optimization rules: MATCH -> pushdown Planning Strategies Graph Execution Code Gen JIT Cost model Storage 包裹，对外提供足够的接口 i32 i64 u32 u32 string string 定长 变长 高可用技术方案 基于 Chain Replication （ CRAQ ） 算法实现，进行数据副本处理，头 结点写，多结点读，支持读写分离 ，提供更好的并发查询能力 数据高可用实现 Chain Replication 数据高可用方案 服务高可用实现 系统中 Meta ， TS 服务采用主备架 构，基于

Major modes • Iptables • IPVS Iptables mode • How it works • DNAT at PREROUTING chain • SNAT at POSTROUTING chain • Pros • Iptables is widely adopted in popular Linux distributions • Cons • O(N^2) O(N^2) in control plane / O(N) in data plane • Poor in scheduling algorithm • Iptables rules are difficult to debug IPVS mode • Services are organized in hash table • IPVS DNAT • conntrack/iptables SNAT

platform ➔ Wants to extend the financial computation/storage model to general cases • Limites of On-chain VM computation • Limites of MPT • Limites of K-V db Problems of Web3: Technical Viewpoint Financial

vm-virtio: virtio device trait and implementation for virtio primitives such as virtqueues and descriptor chain. crates.io • kvm-bindings: Rust FFI bindings to KVM generated using bindgen. • kvm-ioctls: Safe

Garbage Collection Support61 Monadic Operations for std::optional  New members for std::optional to chain operations on an optional without having to check for them being empty  transform(F)  returns

AuthorizationPolicy metadata: name: require-jwt namespace: istio-system spec: action: ALLOW rules: - from: - source: requestPrincipals: ["testing@secure.istio.io/testing@sec ure.istio "productpage-viewer" namespace: default spec: selector: matchLabels: app: productpage rules: - to: - operation: methods: ["GET"] apiVersion: "security.istio.io/v1beta1" kind: name: "details-viewer" namespace: default spec: selector: matchLabels: app: details rules: - from: - source: principals: ["cluster.local/ns/default/sa/bookinfo-productpage"]

configuration: settings: compression/case/method: zstd ● Zoned deployment, Affinity rules ● AntiAffinity rules ● Service templates Operator Administration: ClickHouse defaults Можно собрать желаемую

CallingConv.h • Don’t throw exceptions across the boundary. Explicitly state/document memory ownership rules. • Consider accepting memory alloc/dealloc callbacks – recall previous recommendation. • Limit implicit

order of dynamic initializations  ❌  Static variables with constant initializers  ✔  Complex rules  Non-trivial for a reader to know whether it’s constant initialization or dynamic initialization