SynapCores Community Edition v2.4.2-ce
Community Edition · free · seamless upgrade from v2.4.x
Point your existing MySQL driver at SynapCores and it just works. v2.4.2-ce makes the MySQL-wire endpoint behave the way off-the-shelf clients expect, and hardens concurrent compare-and-swap writes so worker-lease and optimistic-locking workloads are correct under load. If you evaluated the wire protocol before and hit driver friction or a flaky concurrent write, re-run your verification suite — the behavior you expected is now the behavior you get.
The job this removes
Standing up a production control plane on a MySQL-compatible database shouldn't mean
rewriting your storage adapter around the database's quirks. Teams expect to install their
driver of choice — mysql2, a JDBC pool, an ORM, a BI tool — point it at the endpoint, and
have it connect, probe, and run parameterized CRUD. v2.4.2-ce makes that the default
experience.
Off-the-shelf MySQL drivers connect and run, no workarounds
- String escaping matches MySQL semantics. The server advertises its escaping mode in the handshake, so clients that interpolate parameters — the default for most drivers — stop mis-parsing strings that contain quotes or backslashes.
- Connection-pool probes answer on every path.
VERSION(),@@versionand similar readiness checks resolve whether a client issues them as a plain query or a prepared statement, so pools that probe on connect initialize cleanly. - Numbers bind into integer columns. A plain application number writes cleanly into
BIGINT/INTEGERcolumns from any driver — no hand-managing wire types in the app.
Concurrent compare-and-swap is correct under load
The backbone of control planes, job queues, and lease-based coordinators is the conditional
update — UPDATE … SET v = v + 1 WHERE id = ? AND v = ?. Under concurrent writes to the
same table, a narrow correctness gap could previously cause a later read to come back wrong.
That is fixed:
- Conditional updates match the rows they should after concurrent activity on the table.
- Writes that report success store the value you wrote — no silent nulls on constrained columns.
- Reads of a contended table stay consistent instead of erroring.
This closes the highest-severity items from a field report and is the headline reason to upgrade for anyone running concurrent read-modify-write workloads over the wire.
Upgrade advisory. This correctness gap was present in v2.4.1-ce and earlier. If you run concurrent read-modify-write or compare-and-swap workloads over the MySQL-wire endpoint, we recommend upgrading to v2.4.2-ce promptly. Workloads without concurrent writes to the same table are unaffected.
Smoother session recovery
After dropping the database a session was using, subsequent statements fall back to a surviving database instead of pinning to the one that no longer exists — so recovery, including recreating that database, works without a manual reconnect.
Proof
- A production control-plane acceptance suite that previously stalled on the wire endpoint now passes its wire checks end to end.
- Our wire-compatibility acceptance suite: 6/6, validated against the published image.
- Zero SQL-plane performance regression — v2.4.2-ce is equal-or-faster than v2.4.1-ce across point-select, insert, and compare-and-swap, measured release-vs-release.
- Zero feature regressions — full state-asserting validation identical to v2.4.1-ce.
Upgrade
Community Edition, free. Multi-arch Linux (amd64 + arm64) and Apple Silicon.
docker pull synapcores/community:latest # or :v2.4.2-ce
Existing deployments upgrade in place — no data migration, no config change. Concurrent read-modify-write workloads over the wire should upgrade promptly (see the advisory above). If you gated a MySQL-wire rollout behind a verification suite, this is the build to re-run it against.