explaingit

datalinkdc/dinky

Analysis updated 2026-07-03

3,732JavaAudience · dataComplexity · 4/5LicenseSetup · hard

TLDR

A browser-based platform for writing, testing, and managing Apache Flink SQL streaming jobs, with a built-in editor, debug previews, job monitoring, savepoints, and connections to a wide range of databases.

Mindmap

mindmap
  root((Dinky))
    What it does
      Flink SQL web IDE
      Job management
      Data lineage
    Editor features
      Autocomplete
      Syntax checking
      Debug preview
    Deployment targets
      Local machine
      Yarn cluster
      Kubernetes
    Integrations
      MySQL PostgreSQL
      ClickHouse Doris
      Hive Oracle
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Write and submit an Apache Flink SQL streaming job from a browser using the built-in editor with autocomplete and syntax highlighting.

USE CASE 2

Preview a Flink SQL query's output on a small sample before running it on a full production cluster to catch errors early.

USE CASE 3

Monitor running Flink jobs, view logs, take savepoints for recovery, and configure failure alerts from the operations dashboard.

USE CASE 4

Connect to multiple external databases like MySQL, PostgreSQL, or ClickHouse and trace data lineage to see which source fields feed each output column.

What is it built with?

JavaApache FlinkSpring BootMyBatis PlusMonaco Editor

How does it compare?

datalinkdc/dinkyyanzhenjie/nohttpirisshaders/iris
Stars3,7323,7303,727
LanguageJavaJavaJava
Setup difficultyhardeasymoderate
Complexity4/52/53/5
Audiencedatadevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires a running Apache Flink cluster and Java environment, primary documentation and community are Chinese-language.

Use freely for any purpose, including commercial use, as long as you keep the Apache 2.0 copyright and license notices.

In plain English

Dinky is a browser-based platform for writing and running SQL jobs on Apache Flink, a system for processing streams of data in real time. If your company needs to move, transform, or analyze data as it flows from one system to another, Flink does that processing, and Dinky gives teams a web interface to write and manage those jobs without working entirely from the command line. The built-in editor includes autocomplete, syntax highlighting, and a debug preview that lets you see what a query's results look like before the job runs at full scale. Queries can be submitted to a range of deployment environments, including local machines, standalone clusters, Yarn-managed clusters, and Kubernetes clusters, depending on what infrastructure your team already runs. A syntax checker and a plan viewer show how a query will be executed step by step before anything is committed. Beyond writing SQL, the platform includes an operations dashboard where teams can monitor running jobs, view logs, take savepoints (snapshots that preserve the state of a long-running job), configure alerts, and inspect data lineage, which shows which fields in your output came from which source tables. Dinky connects to a wide range of external databases and systems, including ClickHouse, Doris, Hive, MySQL, Oracle, PostgreSQL, and SQL Server, so it can sit at the center of a mixed data environment. The project is open source under the Apache 2.0 license and written primarily in Java. It is built on top of Apache Flink and relies on other open-source libraries including Spring Boot, MyBatis Plus, and Monaco Editor, which is the same code editor that powers VS Code. The README is written mostly in Chinese, so the primary community and documentation are Chinese-language, though an English README is also linked. The planned roadmap includes multi-tenant support, global lineage analysis, and unified metadata management.

Copy-paste prompts

Prompt 1
I have an Apache Flink cluster on Kubernetes. How do I connect Dinky to it and submit a Flink SQL job that reads from Kafka and writes to MySQL?
Prompt 2
How do I use Dinky's debug preview feature to test a Flink SQL query on a small data sample before submitting it to the full cluster?
Prompt 3
How do I configure Dinky to take a savepoint of a long-running Flink streaming job and restore from it after a failure?
Prompt 4
How do I set up Dinky's data lineage view to trace which source table columns are used to produce each column in my output table?

Frequently asked questions

What is dinky?

A browser-based platform for writing, testing, and managing Apache Flink SQL streaming jobs, with a built-in editor, debug previews, job monitoring, savepoints, and connections to a wide range of databases.

What language is dinky written in?

Mainly Java. The stack also includes Java, Apache Flink, Spring Boot.

What license does dinky use?

Use freely for any purpose, including commercial use, as long as you keep the Apache 2.0 copyright and license notices.

How hard is dinky to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is dinky for?

Mainly data.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub datalinkdc on gitmyhub

Verify against the repo before relying on details.