SingleStore SQL binding

[AdalbertMemSQL]

Hi Bun team 👋

I’m exploring the idea of adding SingleStore SQL support directly in Bun and wanted to get early feedback on whether this aligns with Bun’s direction before going too far.

SingleStore is a distributed, real-time SQL database designed to handle both transactional (OLTP) and analytical (OLAP) workloads in a single system. It combines row-based and column-based storage, supports horizontal scalability, and is optimized for high-throughput, low-latency queries.

SingleStore is MySQL wire-compatible, allowing it to work with MySQL clients and tools, but it also introduces implementation differences and extensions for certain features and execution semantics.

From an integration standpoint, this could be implemented either as an extension of Bun’s existing MySQL native binding or as a separate native integration that shares protocol-level components while exposing SingleStore-specific capabilities where appropriate.

I’m happy to do the implementation and maintenance work; mainly looking for early direction to ensure this is aligned with Bun’s design goals and expectations.

Thanks for your time.

[mergisi]

This is a fantastic proposal! Adding native SingleStore support to Bun would be a great addition for developers building high-performance applications.

Why this makes sense for Bun:

1. HTAP workloads: SingleStore's ability to handle both OLTP and OLAP in one system aligns well with Bun's "all-in-one" philosophy. Developers can build real-time analytics dashboards without juggling multiple database connections.
2. Performance synergy: Bun is already focused on speed, and SingleStore is optimized for low-latency queries. Native binding would eliminate the overhead of going through generic MySQL adapters.
3. Growing adoption: SingleStore is gaining traction in the real-time analytics space, especially for use cases like:
4. • Real-time dashboards
5. • IoT data processing
6. • Financial transactions with instant reporting
     Implementation thoughts:

Given SingleStore's MySQL wire compatibility, I'd suggest starting with extending the existing MySQL binding (Option 1) and then adding SingleStore-specific features incrementally:

// Potential API surface
import { singlestore } from "bun:singlestore";

const db = singlestore({
  host: "localhost",
  // SingleStore-specific options
  pipeline: true,  // Enable pipelining
  columnstore: true // Optimize for columnstore queries
});

// Leverage SingleStore's parallel query execution
const results = await db.query`
  SELECT * FROM analytics 
  WHERE timestamp > ${startDate}
`;

For developers working with SQL across different databases (MySQL, PostgreSQL, SingleStore), tools like AI2sql can help generate optimized queries - but having native Bun bindings would make the execution side seamless.

Would love to see this land! Happy to help test when you have a prototype.