Big Data 20 min read

Graph Language and GeaFlow DSL for Integrated Graph‑Table Analytics in Ant Financial

The article presents Ant Financial's practice of graph language and the GeaFlow DSL, covering graph models, query languages, DSL design, architecture, performance optimizations, distributed execution, binary data handling, and future roadmap for unified graph‑table analytics.

DataFunTalk
DataFunTalk
DataFunTalk
Graph Language and GeaFlow DSL for Integrated Graph‑Table Analytics in Ant Financial

This talk introduces graph language concepts and their applications, describing graph models (property graphs, attribute graphs) and comparing their expressive power and performance advantages over relational tables.

It reviews major graph query languages such as Gremlin and ISO/GQL, highlighting their pattern‑matching semantics and the lack of a unified standard, and explains why GeaFlow adopts both Gremlin and ISO/GQL.

The speaker outlines typical use cases in social networks, collaborative recommendation, and financial risk control, emphasizing the need for integrated graph‑table processing.

GeaFlow is presented as Ant's real‑time graph computation engine, detailing its evolution, architecture (SQL plus, unified parser, logical/physical plans, graph optimizer, runtime) and the DSL that unifies graph construction, SQL, and Gremlin/ISO‑GQL queries.

Key design aspects of the DSL include syntax for CREATE GRAPH and INSERT statements, support for both batch and streaming execution, and the ability to express complex graph‑table workflows in a single language.

Performance optimizations are discussed, covering distributed execution of complex graph queries via an enhanced DAG model with jump operators and sub‑DAGs, full‑link binary data formats to reduce serialization overhead, and graph‑table optimizer techniques such as predicate push‑down and column pruning.

Future plans involve extending DSL syntax, adopting native and vectorized execution, tighter integration with data lake and Kafka ecosystems, and improving CBO path‑matching optimization.

The Q&A section clarifies that GeaFlow’s SQL is based on Apache Calcite, ISO/GQL is a subset of the ISO standard, and that the engine focuses on low‑latency, non‑transactional graph analytics rather than strict ACID guarantees.

Big DataDSLreal-time analyticsgraph computinggraph query languageGeaFlow
DataFunTalk
Written by

DataFunTalk

Dedicated to sharing and discussing big data and AI technology applications, aiming to empower a million data scientists. Regularly hosts live tech talks and curates articles on big data, recommendation/search algorithms, advertising algorithms, NLP, intelligent risk control, autonomous driving, and machine learning/deep learning.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.