Hi Zoi, Juri, and the Wayang community, My name is Juan, and I am a Computer Science Engineering student at ESPOL (Escuela Superior Politécnica del Litoral) in Guayaquil, Ecuador. I am writing to express my interest in WAYANG-54 as part of my GSoC 2026 application.
Relevant background: * Data pipeline engineer using PySpark and Databricks for retail analytics * ERP Application Intern at Banco Guayaquil, one of Ecuador's largest banks * Teaching Assistant for Java and Python courses at ESPOL * Mentor for 200 scholarship recipients in a national Data Foundations Program (ESPOL + MINTEL) For my proposal, I am planning a focused 175-hour scope targeting Trino as a single backend. Trino is fully open source, supports Docker-based local testing, and is architecturally compatible with Wayang's existing JDBC abstraction layer — which minimizes new code surface and makes the implementation easier to maintain. The scope would cover the backend abstraction layer, operator mapping, and cost model integration, with a Docker Compose setup for local reproducibility. Does this direction align with what the community has in mind? As an optional addition, I am considering a small benchmark comparing query execution through the Wayang-Trino backend versus raw Trino, to quantify the abstraction overhead. Would this be valuable to the community? I have already cloned the repository and am exploring the existing platform implementations. Thank you for your time. I look forward to engaging with the community. Best regards, Juan ESPOL
