The Hong Kong Databricks FSI Community Day 2026 stands out as a highly unique, independent gathering happening directly within the Hong Kong Island waters. Operating away from typical convention centers, this exclusive, invitation-only event takes place entirely aboard a private boat traveling along the local ferry route. The forum serves as a dedicated working exchange for professionals operating at the intersection of complex data streams, financial markets, risk modeling, and institutional oversight.
To maintain absolute psychological and operational safety for its attendees, the organizers have stripped away traditional corporate hierarchies and product pitches in favor of open, critical peer challenges. There are no speaker names, titles, or recording devices permitted on board, ensuring that all field briefings focus strictly on executable expertise rather than corporate branding. Over thirty distinct technical proposals detail real-world financial architectures, handling everything from cross-border liquidity management and real-time streaming calculation paths to data isolation between entities in Hong Kong and Singapore. This community-driven event remains entirely independent of Databricks corporation, functioning instead as a private, expert-led ecosystem for practitioners navigating the realities of fragmented regional market structures.
Event Page:
https://vertexmacro.com/events/databricks_community_day_2026/index.html
Group Page:
https://usergroups.databricks.com/hong-kong-databricks-fsi-group/
Topic:
Engineering an LTAP Control Plane for Onsite Trading Robots Across Asian Markets
Focus:
Architecture-Focused
Speaker Background:
From music-production houses and live-brand keyboard performance to proprietary-firm DevOps field engineering, the speaker leads onsite trading-robot deployments. The speaker combines real-time synchronization, disciplined rehearsal, production reliability, exchange connectivity, incident response, and infrastructure automation to build institutional-grade trading systems for Asian markets.
Description:
An onsite trading robot is an operational system, not merely an algorithm. It must receive market data, evaluate strategy state, submit and cancel orders, persist configuration, track positions, respect limits, expose health, and support immediate human intervention. Across Asia, the same robot may face different exchange protocols, colocation facilities, trading calendars, tick sizes, throttles, auction rules, currencies, network paths, and regulatory controls. A system that performs well in a laboratory can fail when market-open traffic, partial connectivity, stale reference data, or an uncontrolled retry loop meets real capital.
This session presents an institutional-grade architecture using Databricks Lake Transactional/Analytical Processing, Lakebase Postgres, Lakehouse Real-Time, and Unity Catalog. LTAP is treated as an architecture rather than a single feature. It brings transactional and analytical workloads closer through a unified storage and governance model, reducing the separate CDC, replication, and serving systems traditionally required to keep application state and analytics aligned. Availability and implementation vary by cloud, region, and product maturity, so the blueprint defines production and fallback paths explicitly.
Lakebase supplies the operational Postgres interface familiar to application developers. It stores robot configuration, strategy deployment records, order intent, workflow state, acknowledgements, operator actions, incident cases, and approved control parameters. Its compute and storage layers are separated: stateless Postgres compute works with safekeepers, pageservers, and durable cloud object storage. This supports autoscaling, branching, read replicas, recovery, and scale-to-zero patterns without forcing the robot team to invent a proprietary operational database interface.
The architecture does not place the exchange execution loop behind a remote analytical query. Latency-critical market-data handling, pre-trade checks, order routing, and kill switches remain onsite or in certified colocated infrastructure. Lakebase receives durable operational state and supervisory events through controlled asynchronous interfaces. The robot must continue in a safe degraded mode if cloud connectivity is interrupted. Local limits, message throttles, sequence checks, duplicate protection, cancel-on-disconnect, and venue-native emergency controls remain enforceable without Databricks.
For analytical access, LTAP capabilities can make Postgres changes available as Delta history without a separately managed external CDC tool. Where a capability is in preview or unavailable, the design uses a documented managed pipeline and reconciliation process. The objective is not to claim that all data movement disappears. It is to remove avoidable copies while proving completeness, order, latency, replay, and recovery for every authoritative stream.
Lakehouse Real-Time provides a serverless, low-latency, high-concurrency analytical serving layer over governed Delta Lake and Apache Iceberg tables. Powered by the Reyden engine, it is designed for operational analytics, custom applications, dashboards, and agent workloads that need sub-second responses. It serves robot health, trading exposure, execution quality, venue behavior, order-to-trade ratios, latency percentiles, rejected orders, inventory, mark-outs, and control breaches to line managers, risk, operations, and engineering without creating another proprietary serving store.
The end-to-end blueprint uses six planes. The edge plane hosts exchange gateways, local market data, robot processes, and certified controls. The transactional plane persists operational state in Lakebase. The analytical plane stores event history and derived measures in open tables. The real-time serving plane uses Lakehouse//RT for high-concurrency reads. The governance plane uses Unity Catalog for permissions, discovery, and lineage. The resilience plane covers buffering, idempotency, sequence recovery, reconciliation, regional failover, clock synchronization, and disaster exercises.
A live incident follows an algorithm that begins repeating orders after a venue acknowledgement delay. Edge controls detect abnormal message rate and activate the local brake. Lakebase records robot state, operator acknowledgement, and the incident workflow. Analytical tables reconstruct market conditions, request and response sequences, exposure, and residual orders. Lakehouse//RT distributes a current, permission-aware view to hundreds of stakeholders. The team can determine whether the cause was exchange latency, strategy logic, duplicate retry, stale configuration, or network behavior.
Production readiness requires deterministic deployment artifacts, signed configuration, infrastructure-as-code, hardware and kernel baselines, exchange certification, canary rollout, replay tests, chaos exercises, capacity baselines, recovery objectives, and complete audit evidence. The field engineering lead treats every release like a live performance: instruments tuned, channels tested, timing synchronized, fallback rehearsed, and one accountable conductor empowered to stop the show.
Audience Takeaways:
Participants receive an Asia-focused LTAP reference architecture covering onsite robot boundaries, Lakebase transactional state, Delta event history, Lakehouse//RT analytics, Unity Catalog governance, and resilient edge-to-cloud integration. They will understand where pipelines can be removed, where reconciliation remains mandatory, and how to preserve local kill switches, deterministic recovery, and capital protection during failures.
Top comments (0)