GitHub user lkskjjk added a comment to the discussion: [DISCUSS] [GSoC 2026] Proposal on Enhancing Multi-Database AT Mode Support for Apache Seata-Go
My decision is to use godror based on the following research: * Production-Grade Stability: godror is built upon the official Oracle ODPI-C layer. Unlike community-driven pure-Go alternatives, it provides the deterministic transaction boundary control required for Seata’s AT mode, minimizing the risk of edge-case failures in high-concurrency financial environments. * Efficient LOB Streaming: Capturing Before/After Images for large objects (CLOB/BLOB) is memory-intensive. godror integrates directly with the native Oracle client to support chunked streaming. This is essential to prevent heap memory spikes (OOM) during transaction snapshots, which a pure-Go implementation would struggle to handle efficiently. * Session-Level Precision: Distributed systems are prone to timezone and locale drifts. godror offers superior control over session-level parameters (e.g., NLS settings). This ensures the precision of DATE and TIMESTAMP types remains immutable across diverse server locales, preventing data corruption during the UndoLog serialization process. GitHub link: https://github.com/apache/incubator-seata-go/discussions/1110#discussioncomment-16601776 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
