Login

u/Only-Ad1737

r/dartlang r/FlutterDev r/Zig
▲ 13 r/dartlang+1 crossposts

Shipped a pure Dart SQL Server driver

Shipped mssql — a pure Dart TDS 7.4 driver for SQL Server. No FFI, no native extensions, just Dart and TCP.

Features: named params, connection pool, TLS, Azure AD auth, multiple result sets, streaming, transactions. 366 tests including concurrent pool stress tests and adversarial comparison against go-mssqldb and node-mssql.

dart pub add mssql

It works as a standalone driver today. The next step is switching knex_dart_mssql to use it as the underlying transport — which drops the C FFI dependency and makes the knex_dart MSSQL driver work on web.

github.com/kartikey321/mssql-dart | pub.dev/packages/mssql

u/Only-Ad1737 — 11 days ago
▲ 6 r/dartlang+1 crossposts

knex_dart is looking for contributors — come help build out SQL tooling for Dart

knex_dart started as a port of Knex.js. Over time it has grown into something more than that - it takes the battle-tested API design and query-building maturity that Knex.js built over a decade and carries it forward for Dart and Flutter, with drivers, features, and platform targets that Knex.js itself never had to think about.

Today the project has eight drivers: PostgreSQL, MySQL, SQLite (native + WASM, with reactive watch() streaming), DuckDB, SQL Server, BigQuery, Snowflake, Turso/libSQL, and Cloudflare D1. Around that core there is an OpenTelemetry integration, a custom lint plugin with 15 dialect-aware static analysis rules, a browser playground for trying queries interactively, and a Jaspr-based docs site.

The codebase moves fast and the foundation is solid. What we need now is depth — and that is where contributors come in.

There is meaningful work at every level:

  • Docs and examples — every driver has a story to tell and most pages have room for better examples, cross-links, and real-world snippets. Good docs are what turns "interesting project" into something people actually adopt.
  • Driver depth — each driver can go further: more complete schema compiler coverage, edge-case query handling, better error messages, performance tuning.
  • Playground and snippets — more interactive examples that show what each driver and feature can do.
  • Agent skills — the repo uses Claude Code skills (.claude/skills/) to encode contributor workflows. There is room to extend these.
  • Tests — more integration test coverage, especially around schema operations, NULL handling, and nested transactions.

If you want to dig into something harder, there are also active engineering projects around driver internals — but those are not a requirement. There is plenty of high-value work that does not require knowing a wire protocol.

The architecture is documented in AGENTS.md and the playground is at https://playground.knex.mahawarkartikey.in.

Repo: https://github.com/kartikey321/knex-dart

Open an issue, leave a comment here, or DM me. Happy to point you at something that fits what you want to work on.

reddit.com
u/Only-Ad1737 — 14 days ago
▲ 6 r/dartlang+2 crossposts

Opened Dart SDK discussion on server runtime hot-path overhead (dart-zig PoC + benchmarks)

I opened a Dart SDK issue here: https://github.com/dart-lang/sdk/issues/63352

This is a discussion about backend runtime architecture for high-concurrency HTTP workloads.

I built an experimental PoC (dart-zig) where Dart stays at handler/business-logic level, and some HTTP hot-path runtime work is native- side (event loop, request framing/parsing, batched completions, process-per-worker with SO_REUSEPORT).

Initial HttpArena snapshot (AOT, throughput-focused):

Test Conn dart:io RPS dart-zig RPS Relative
baseline 512 601,780 1,353,265 ~2.25x
baseline 4096 583,020 1,665,927 ~2.86x
pipelined 512 998,153 1,364,400 ~1.37x
pipelined 4096 997,674 1,477,162 ~1.48x

Notes:

  • This is an initial PoC snapshot for directional signal.
  • Memory footprint is not optimized yet.
  • Claims are limited to HTTP hot-path behavior.

Also important: this is not a “replace dart:io” claim. I’m trying to discuss whether an official/experimental server-optimized runtime profile could make sense for Dart backend workloads, and what upstream criteria/hook points would be appropriate.

Would love feedback from people doing high-load Dart backend work.

u/Only-Ad1737 — 2 months ago