Releases: voutilad/bolt-proxy
v0.4.0 - the Just In Time release
Major change is modifying the RoutingTable stuff to be fetched on-demand (if uncached or expired) similar to the way drivers handle it today. Some spurious issues still in a clustered environment with read replicas and going through a SSR setup, but more stable and tends to "just work" a bit better.
Why do I continue with this stuff? No idea.
v0.3.0 - The Just In Case Release
There's not much need for bolt-proxy
in this world, hopefully, but just in case I've fixed some things:
- preserve chunks for direct bolt connections (no more dechunking thus preventing blowing up buffers)
- fix some under-reads triggered by websocket connections
- fix how backend versions are extracted in order to work with Aura
- fix how routing tables are acquired to work properly with server-side routing (SSR) configurations
It's now possible to do horrible things with this layer 7 proxy and I'm not sure I should be proud or terrified.
v0.2.0 - Can't stop, won't stop
So much fun in this one:
- cleaner logging hiding most chatter behind a debug mode
- super basic health check...send a
GET
to/health
on the port - negotiates client versions, no longer pinning all clients to bolt v4.1
- support for clients and servers from v4.0.0 and newer!
- tweaked Dockerfile to default bind to 0.0.0.0 because Docker
v0.1.0 - Beta for testing with Aura and GKE
While there are still many rough edges and design trade-offs, this cut should be ready for a beating. Provided source-only for now as it's all pure Go, so a simple go build
is all you need.