Nov 21, 12:00 – 1:30 PM (HKT)
1 RSVPs

Engineering a Governed Asia FX Carry Platform with Databricks Lakeflow
Architecture-Focused
Former military combat engineer turned institutional-grade trader, providing currency-pair and carry-trade analysis for a China-focused trading desk. The speaker applies mission planning, redundancy, controlled execution, and after-action discipline to the design of production-grade FX data systems for institutional trading.
Asia FX trading is a distributed systems problem as much as a market problem. A China-focused desk must combine onshore and offshore renminbi markets, regional currencies, interest-rate curves, forward points, fixing calendars, central-bank events, liquidity conditions, funding costs, collateral data, counterparty limits, and operational records. These inputs arrive at different speeds and in different formats. They are also governed by different legal entities, market-access arrangements, licensing terms, and data-residency requirements. A carry opportunity that looks attractive from spot and forward prices alone can disappear after hedging costs, cross-currency basis, execution slippage, holiday mismatches, balance-sheet charges, and stressed unwind assumptions are included.
This session presents a reference architecture built around the Databricks Lakeflow declarative framework. Lakeflow Connect forms the ingestion layer for databases, SaaS applications, file sources, and streaming systems. Its ecosystem of more than 100 built-in connectors can bring together trading and risk data with enterprise context from sources such as Salesforce, Workday, and other operational platforms. Managed ingestion pipelines use incremental reads and writes, serverless execution, and Unity Catalog integration to reduce the custom connector code and infrastructure traditionally required to keep regional data current.
The proposed architecture separates the platform into six governed zones. The source zone receives spot, forward, swap, curve, benchmark, macroeconomic, position, order, execution, collateral, and operational data. The ingestion zone uses managed connectors, change data capture, file ingestion, streaming interfaces, and data contracts. The declarative processing zone defines quality expectations, dependencies, transformations, and recovery behavior as maintainable pipelines rather than a collection of fragile scripts. The trusted-data zone publishes standardized currency-pair, tenor, curve, holiday, fixing, counterparty, and legal-entity datasets. The serving zone supplies trader analytics, APIs, risk dashboards, and research workloads. The governance zone uses Unity Catalog for permissions, discovery, lineage, auditability, and ownership.
A detailed data path follows a CNH carry signal from source to decision. Lakeflow ingests spot and forward quotes, short-term rate curves, offshore funding indicators, order and fill data, and approved market calendars. Declarative pipelines normalize currency conventions, align timestamps, validate bid-ask relationships, identify stale observations, manage late data, and calculate forward-implied yields. The curated layer then calculates carry, roll-down, cross-currency basis, transaction-cost-adjusted return, volatility-scaled return, expected drawdown, liquidity score, and stress unwind cost. Desk applications consume only governed and quality-scored outputs, while the raw observations and transformation lineage remain available for replay and investigation.
The session explores how automatic platform upgrades should be controlled in an institutional environment. Lakeflow Pipelines can operate in a versionless model in which Databricks manages runtime upgrades. This reduces manual patching, but a bank or trading firm still needs preview-channel testing, regression datasets, data-quality gates, performance baselines, rollback procedures, dependency controls, and formal production acceptance. The design therefore introduces a certification pipeline that evaluates upcoming changes against representative China-desk workloads before wider adoption.
Participants will leave with a production-oriented Lakeflow architecture for Asian FX pair and carry analytics, a clear ingestion-to-serving data path, patterns for declarative quality and recovery, a controlled automatic-upgrade framework, and practical governance measures for Unity Catalog managed tables, VARIANT data, and cross-jurisdiction trading information.

Turning Fragmented Asian FX Data into Governed Carry Decisions with Databricks Lakeflow
Business and FSI-Focused
Former military combat engineer turned institutional-grade trader who provides currency-pair and carry-trade analysis to a China-focused trading desk. The speaker combines operational discipline with practical knowledge of funding, liquidity, market structure, and the controls required to convert an apparent FX opportunity into an institutional decision.
Carry trading is often described as borrowing in a lower-yielding currency and investing in a higher-yielding currency. On an institutional China trading desk, the real decision is much more demanding. The desk must determine whether expected carry survives forward pricing, cross-currency basis, hedging expense, execution cost, volatility, liquidity withdrawal, policy shocks, capital treatment, counterparty exposure, settlement constraints, and the cost of exiting during stress. The answer depends on fresh data from both trading systems and business systems, with enough lineage to explain the decision later.
This session proposes a business operating model using Databricks Lakeflow to connect market, risk, treasury, finance, operational, and control data. Lakeflow Connect provides managed ingestion across more than 100 built-in connectors spanning enterprise applications, databases, files, and streaming sources. Connectors for platforms such as Workday and Salesforce allow business context to be analyzed beside trades, positions, and market data. Where a required platform or specialized source is not available as a managed connector, community or custom connector patterns preserve the same governance and operational model rather than forcing the desk into an unmonitored data silo.
The central use case is an Asia FX carry decision cockpit. Traders see spot, forwards, implied yield, basis, liquidity, realized and implied volatility, expected transaction cost, and scenario-adjusted return. Treasury sees projected cash flows, collateral consumption, funding concentration, and intraday liquidity. Market risk sees sensitivities, drawdown, gap risk, stress loss, and correlated exposure across currency pairs. Operations sees confirmations, settlement instructions, failed trades, fixing events, and holiday mismatches. Compliance and model-risk teams see the source, transformation, owner, quality status, and approval history behind every material metric.
Lakeflow's declarative approach changes the operating model. Teams define the desired datasets, quality expectations, and dependencies, while the platform manages execution and dependency handling. This reduces the burden of maintaining isolated ingestion scripts and makes quality rules visible to both engineers and control functions. A rule can quarantine inverted markets, reject impossible forward tenors, flag stale curves, detect absent fixings, or prevent a signal from reaching production when required data is incomplete. The purpose is not to automate trading judgment. It is to ensure that judgment is based on consistent, timely, and explainable information.
The session maps technical capabilities to measurable FSI value. Managed connectors shorten the time required to onboard a regional system. Incremental ingestion reduces unnecessary data movement. Declarative processing lowers maintenance effort and makes controls repeatable. Unity Catalog helps standardize ownership, access, lineage, and audit evidence. Automatic upgrades can reduce platform debt when supported by disciplined testing. Row Tracking, Checkpoint V2, and Deletion Vectors can support more efficient change processing and table maintenance. Variant shredding can improve access to frequently queried fields in semi-structured market or operational payloads, subject to runtime and reader compatibility.
The Asia focus is explicit rather than generic. The proposal examines CNY and CNH relationships, Asian dollar funding, regional rate differentials, offshore liquidity, central-bank policy divergence, local holidays, benchmark timing, and the impact of different market-access and settlement arrangements. It also highlights that regional diversification can fail during stress because correlations, dollar demand, and liquidity premiums can change together.
Participants will gain an executive-to-desk business case for Lakeflow, a China and Asia FX use-case map, a governance model connecting front office and control functions, and a phased value framework grounded in execution quality, funding efficiency, operational resilience, and explainability.
Hong Kong Databricks FSI Community Day Event Page:
https://vertexmacro.com/events/databricks_community_day_2026/index.html
Frontier Capital
Macro Trader
Investor Group
Financial Officer ASZEN
Financial Group
Tech Lead
AWS
User Group Leader, Guangzhou
Frontier Capital
Senior Asset Manager
Frontier Capital
Macro Trader
AWS
User Group Leader, Guangzhou
Investor Group
Financial Officer ASZEN
Frontier Capital
Senior Asset Manager
Financial Group
Tech Lead