The Omega real‑time reach system uses a custom DSL that unifies input data, standardizes CEP APIs, and leverages an Antlr V4‑based translation framework to generate Python, C++, JavaScript, and Java code for cloud, edge, and front‑end containers, cutting rule development from days to minutes.
The article chronicles a multi‑year effort to build a universal language model that can convert any source programming language into any target language, detailing experiments with Go‑ANTLR, Kotlin‑ANTLR, regex‑based parsing, DSL design, and the emerging Charj language and its tooling.
This article explains how to separate Elasticsearch DSL queries from application code by defining reusable search templates with Mustache placeholders, managing them via the scripts API, and rendering them with parameters to produce flexible, maintainable search requests.
This article explains why a terms query with an array fails inside an Elasticsearch search template, demonstrates the correct Mustache‑based template syntax, and provides step‑by‑step code examples for defining the index, inserting data, creating the template, and executing the query.
This article explains how to treat Domain‑Driven Design as code by leveraging ContextMapper's DSL to model strategic and tactical aspects, define subdomains, bounded contexts, context maps, and generate consistent documentation and code artifacts for microservice architectures.
The article explains how Alibaba Cloud’s new DSL, Darabonba, redefines OpenAPI metadata to generate multi‑language SDKs, modular interface designs, automatic code‑sample creation, and test case generation, addressing common OpenAPI usability issues such as missing SDKs, inconsistent styles, and lack of runnable examples.
This article details how Ctrip's hotel search system was optimized through storage compression, spatial indexing, KV storage, semantic query generation, context‑aware error correction, and a custom domain‑specific language, balancing performance, flexibility, and user experience for large‑scale online travel services.
The article explains how to use Groovy's operator‑overloading features to create a JSONPath‑style verification DSL, detailing which operators are implemented, the challenges with sign‑conversion operators, and providing a full example class with logging for each overloaded operator.
This article explores Alibaba’s effort to automate code generation by converting product requirements into standardized design language and leveraging AI and machine learning to bridge the gap between natural language specifications and executable frontend code.
The article details Meituan’s Flap system, a static‑DSL‑based dynamic Flutter architecture that converts Dart code into JSON, loads it at runtime, and delivers cross‑platform, low‑cost, high‑performance updates, reducing package size and release cycles while preserving native Flutter rendering quality.
This article walks through using Elasticsearch SQL to query data, covering installation, loading sample datasets, describing index schemas, executing simple and complex SQL queries with functions, converting SQL to Elasticsearch DSL, reindexing, alias management, and performance considerations, all illustrated with code snippets.
This article details JD Shanghai's mobile team exploration of a dynamic UI solution that uses a custom domain‑specific language (DSL) to enable cross‑platform (iOS, Android, H5) page publishing without client updates, describing design goals, architecture layers, template management, event handling, performance optimizations, and real‑world deployment.
This article explains the concept and benefits of domain‑specific languages, classifies DSL types, and demonstrates how to implement a lightweight, stateless state‑machine engine in Java using a fluent internal DSL that improves code readability, maintainability, and performance.
This article describes how Alibaba Cloud’s front‑end and marketing platform team tackled frequent urgent requests and front‑end bottlenecks by adopting component‑based development and intelligent Design‑to‑Code tools like imgcook, resulting in significant automation, reduced manual effort, and a scalable low‑code workflow.
To accelerate growth on Xianyu’s 20 million‑DAU platform, the team built an event‑driven rule engine with a SQL‑like DSL that translates user‑behavior streams into real‑time Flink/Blink queries, cutting rule development from four days to half a day and achieving sub‑5‑second processing latency.
The article details Xianyu’s real‑time complex event processing system, which abstracts diverse business scenarios—such as activity coupons, price‑drop alerts, rental suggestions, and promotional offers—into a rule‑driven pipeline comprising log collection, a Blink‑based DSL EPL engine, and configurable result delivery, enabling feature rollout in half a day with ~10‑second latency.
Xianyu’s Complex Event Processing system, built on Alibaba’s Blink (Flink) and a custom SQL‑like DSL, standardizes event I/O, lets users define sequence, window and aggregation rules, and combines an interactive rule service, SLS source, parser, job manager and MetaQ sink to achieve ~100 k QPS, sub‑second latency, fault‑tolerant, and rule‑to‑production turnaround in about thirty minutes.
By replacing the naïve DSL‑to‑Widget mapping with custom Widget, Element, and RenderObject classes that respect match_parent and match_content semantics and leverage RelayoutBoundary optimizations, the team reduced layout complexity from O(N²) to O(N), boosting long‑list frame rates from about 28 fps to roughly 50 fps while outlining further refinements.
The article describes a pipeline that automatically extracts a JSON‑like DSL representation of Alibaba’s 99‑promotion UI from rendered pages, cleanses CSS, converts transforms, renders the DSL to images, and combines it with dynamic ViewModel data to generate tens of thousands of high‑quality samples per module, raising recognition accuracy above 98%.
This article introduces Kotlin DSL concepts, demonstrates real‑world applications such as Trip.com payment network encapsulation, overseas payment SDK Gradle scripts, Anko layouts, and provides a step‑by‑step example for creating a custom DSL, highlighting benefits, trade‑offs, and best practices for mobile development.
The article presents the FoxPage Native platform developed by Trip.com to address homepage iteration challenges by using a JSON‑based DSL, Flexbox layout, and a modular architecture that enables high‑performance, dynamic, and multi‑device UI rendering with low development cost.
The article describes how Gaode refactored its multi‑endpoint car‑networking services by replacing duplicated REST APIs with atomic GraphQL‑driven services orchestrated through an API gateway, using a lightweight DSL and plugins to handle non‑business concerns, achieving ~60% reduction in custom code and faster development.
Zhihu’s Morph dynamic solution, built on a Flexbox‑based DSL and JSON, enabled rapid, cross‑platform updates of mobile ad cards, dramatically reducing rollout time from eight days to one and supporting over 70 styles with minimal impact on app size and performance.
Gatling‑Dubbo 2.0 is a Gatling‑based load‑testing plugin that replaces generic Dubbo invocations with real API calls, offering richer scenario orchestration, traffic models, native throttling, lower resource use, and higher concurrency, while providing Action, Check, and DSL components illustrated through a complete mixed‑scenario simulation.
The UI2CODE pipeline converts image‑derived JSON DSL layouts into Flutter code by constructing a hierarchical DSL tree, partitioning it into rows, columns or stacks, applying unsupervised text‑alignment and padding heuristics, generating templated widget code with separate data models, cutting development effort by roughly two‑thirds and now used internally at Xianyu.
The Gatling‑Dubbo plugin extends Gatling’s high‑performance, event‑driven load‑testing framework with a Dubbo protocol layer, providing protocol, action, and JsonPath‑based check components plus a HTTP‑like DSL, enabling asynchronous generic calls, response validation, throttling, and full example simulations for distributed Dubbo service testing.
Pirate Middleware introduces a JSON‑based DSL that orchestrates generic service calls across Meituan’s myriad business lines, replacing heavyweight custom adapters with a decoupled, parallel‑or‑sequential execution engine, thereby shifting data preparation to business teams, cutting development effort, and enhancing reuse, monitoring, and overall platform efficiency.
ui‑automation, developed by Alibaba’s Xianyu team, automatically converts Sketch files or PNG images into clean, maintainable UI code for platforms such as Flutter or Weex by extracting visual information, building a hierarchical DSL, and applying template generation, delivering senior‑engineer‑level quality while overcoming the maintainability limits of earlier scanning‑based approaches.
The article explains how treating CI/CD pipelines as code—managed via version control and domain‑specific languages—solves configuration drift, reproducibility, and documentation issues, and outlines practical steps and tool examples for implementing this DevOps practice.
This article explains how Groovy parses Android-specific DSL in Gradle build files, covering DSL benefits, command chains, operator overloading, delegate mechanisms, and step‑by‑step execution of buildscript, repositories, dependencies, and tasks to help developers customize their Android build process.
The article critiques popular but unnecessary log‑analysis features—such as sub‑second alerts, endless pagination, flashy maps, full SQL support, bulk downloads, and live tail—arguing that focusing on practical alert content, efficient querying, and proper architecture yields far more value for IT operations.
This article explains how a financial e‑commerce platform uses the Event Sourcing architecture pattern, an asynchronous message bus, and a Go‑based domain‑specific language to build a flexible, exactly‑once points system that decouples business rules from application code and simplifies operations.
The article describes how Haier’s e‑commerce platform uses a service‑oriented architecture based on Dubbo, a fine‑grained product query DSL, and a highly scalable product service design to handle massive traffic spikes during major shopping events while maintaining performance, extensibility, and reliability.
The article narrates a junior developer’s struggle with a tedious manual build workflow, his creation of a Java‑based BuildTool to automate compilation, packaging, and deployment, and the evolution toward an XML‑driven DSL that eventually inspired the naming of Apache ANT.
